UNIT 9- ASSIGNMENT 2
,Contents
Scope of the Project:.............................................................................................................................4
Methodology for the project:................................................................................................................4
Methodology 1: Waterfall.................................................................................4
Methodology 2: Agile........................................................................................5
Chosen Methodology Justification:...................................................................7
Test Plan (Initial):...................................................................................................................................7
Final Product (Project Development):....................................................................................................8
Work Log:..............................................................................................................................................9
Revised Gantt Chart:............................................................................................................................10
Test Plan (Updated):............................................................................................................................10
Feedback Questionnaires:...................................................................................................................11
Improvements based on feedback:.....................................................................................................13
1-..........................................................................................................................................................13
Researching possible solutions:...........................................................................................................14
Solution 1:........................................................................................................14
Risks and constraints of solution 1:.................................................................15
Constraints: Some of the constraints of using Notepad++ are:......................15
Solution 2:........................................................................................................15
Risks and constraints of solution 2:.................................................................16
Constraints: Some of the constraints of using Visual Studio include:.............16
Dependency on Platform: Visual Studio is mainly meant for Windows devices Although it can
facilitate platform development for certain languages, it might not be the best option for projects
aiming at non-Windows operating systems.........................................................................................16
Licence Fees: There are several editions of Visual Studio, and some of them are not free. Although
the edition is free, a purchased edition is frequently needed for the more complex features and
functionalities......................................................................................................................................16
Integration Difficulties: Additional setups could be needed for integration with some third-party
tools or libraries. Even while Visual Studio offers strong support for a wide range of technologies,
there may be some situations in which whole integration is difficult..................................................16
Complexity of Project Files: Visual Studio can produce complex project files (.csproj for C# projects,
for example). Editing these files by hand can be error-prone, thus may take time.............................16
Justification of final solution:.......................................................................................................16
Feasibility Study:..................................................................................................................................17
,Technical Assessment: The software company's technical resources are the
main focus of the technical assessment of the feasibility study. It assists
companies in determining whether their technical staff is capable of
translating concepts into functional systems and whether their technical
resources are sufficient...................................................................................17
Economic: Usually include a cost/benefit analysis of the project, this
assessment aids organisations in evaluating a project's viability, costs, and
advantages prior to allocating financial resources. ........................................17
Legal: is the process of reviewing a proposed restructuring or steps plan for
possible legal problems and creating a plan to be put into action during the
restructuring's implementation phase so that the planned restructuring
includes a combined and integrated tax and legal assessment. ....................17
Operational: Operational feasibility is the degree to which a proposed system
meets requirements found in the requirements analysis phase of system
development, solves issues, and seizes opportunities found during scope
definition..........................................................................................................17
Scheduling: An organisation calculates the duration of the project in order to
determine its scheduling feasibility. Following a thorough examination of
each of these areas, the feasibility analysis assists in identifying any potential
obstacles to the proposed project, such as: Internal Project Restrictions:
Financial, Resource, Budgetary, and Technical...............................................17
Functional Requirements: The features and capabilities that a system needs
to fulfil its intended purpose are outlined in its functional requirements.
Usually, these specifications are stated in terms of tasks or functions that the
system needs to complete. Functional needs in the context of web
development could be:....................................................................................18
User Authentication: Describing how users will be able to create accounts,
log in, and manage their credentials...............................................................18
User Interface (UI): Describe the user interface's appearance, functionality,
and style...........................................................................................................18
Database Operations: Explain how to retrieve, store, and modify data from
and in the database.........................................................................................18
Functionality of Modules/Components: Describe in detail the attributes of
the various web application modules or components....................................18
, Workflow: Describe the series of actions a user performs inside the system to
complete a task................................................................................................18
Non-Functional Requirements: Non-functional requirements figure the
characteristics or features that the system must possess; they do not,
however, specify particular actions. These specifications put an emphasis on
features like scalability, performance, and usability. Non-functional needs in
web development can include:.......................................................................18
Performance: Indicate throughput, reaction times, and other parameters
linked to performance.....................................................................................18
Scalability: Defined as the system's ability to accommodate growing user
and data demands...........................................................................................18
Reliability: Indicate how well the system will function over an extended
period of time..................................................................................................18
Usability: Specify the needs for a user's experience, such as responsiveness
and ease of use................................................................................................18
Project Plan:.........................................................................................................................................18
Gantt Chart:.........................................................................................................................................18
Storyboard:......................................................................................................19
Flow Chart:..........................................................................................................................................21
Assets Table:........................................................................................................................................22
References:..........................................................................................................................................23
, Project Outline: A company contracted me to develop a fully integrated,
functioning website for their business. A preliminary task was to develop a website that
showcased my skills based on the following requirements.
Client requirements: As an initiation task you have been asked to develop a
web site with the following requirements to showcase your skills. The requirements that are
needed are:
A website with a minimum of 4 pages
Use of hyperlinks
Use of a company logo
Links to social media accounts
Scope of the Project:
The project's business case is improved during the earliest stages, along with the
project's scope. I'll create HTML code as part of my project to create a website that
meets the requirements of my client. This project's goal is to build a completely
functional website for individuals in need of ink cartridges in order to print whether
at home or workplaces for different purposes, all people who use different types of
pens, markers that need ink filling and similar…etc.., including individuals who are
environmentally aware and wanted to use products that are friendly for the
environment, biodegradable and recyclable in order to waste less.
Methodology for the project:
Methodology 1: Waterfall
The waterfall methodology can be useful for a website development project as it follows a
linear and sequential process, it has been widely used in the past, it could be applied by:
Requirements Gathering:
This is done by defining and recording the project's needs. This covers the website's design,
functionality, and any other elements that are necessary.
