ASSIGNMENT 2 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit Number and

Unit 9: Software Development Life Cycle
Title

Date Received 1st

Submission Date
Submission

Re-Submission Date Received 2nd

Date Submission

Student Name Vo Thi Minh Thu Student ID GCD210164

Class GCD1105 Assessor Name Phan Thanh Tra

Student Declaration
I certify that the assignment submission is entirely my own work and I fully understand the
consequences of plagiarism. I understand that making a false declaration is a form of malpractice.

Student’s Signature Thu

Grading Grid

P5 P6 P7 M3 M4 M5 M6 D3 D4
❒ Summative Feedback: ❒
Resubmission Feedback:

Grade: Assessor Signature: Date:

Internal Verifier’s Comments:

Signature & Date:

 Table of Contents
1. Undertake a software investigation to meet a business need (P5).............................................................. 5
1.1. Identify the stakeholders, their roles and interests in the case study ................................................. 5
1.2. FRs and NFRs ...................................................................................................................................... 7
2. Discuss the technique(s) you would use to obtain the requirements.......................................................... 9
2.1. JAD ..................................................................................................................................................... 9
2.2. Story mapping .................................................................................................................................. 11
3. Use appropriate software analysis tools/techniques to carry out a software investigation and create
supporting documentation (P6) ........................................................................................................................ 12
3.1. Context Diagram............................................................................................................................... 12
3.2. Data Flow Diagram ........................................................................................................................... 12
3.3. ERD................................................................................................................................................... 12
3.4. Flowchart ......................................................................................................................................... 14
3.4.1. Search in web ........................................................................................................................... 14
3.4.2. Purchase ................................................................................................................................... 15
4. Explain how user and software requirements have been addressed (P7) ................................................. 16
4.1. Use Case Diagram ............................................................................................................................. 16
4.2. Use Case specification ...................................................................................................................... 16
4.2.1. View/Update detail....................................................................................................................... 16
4.2.2. Update service diagram ............................................................................................................ 16
4.3. Wireframe ........................................................................................................................................ 17
4.4. Mockup ............................................................................................................................................ 22
 Table of Figure
Figure 1: The stakeholders.................................................................................................................................. 5
Figure 2: Types of stakeholders .......................................................................................................................... 6
Figure 3: Compare Functional vs Non Functional Requirement .......................................................................... 7
Figure 4: JAD....................................................................................................................................................... 9
Figure 5: Story mapping.................................................................................................................................... 11
Figure 6: Context Diagram ................................................................................................................................ 12
Figure 7: ERD for Health Connect ..................................................................................................................... 13
Figure 8: Search in web .................................................................................................................................... 14
Figure 9: Purchase ............................................................................................................................................ 15
Figure 10: Use Case Diagram for the whole system .......................................................................................... 16
Figure 11: View/Update detail .......................................................................................................................... 16
Figure 12: Update service diagram ................................................................................................................... 17
Figure 13: Wireframe 1..................................................................................................................................... 18
Figure 14: Wireframe 2..................................................................................................................................... 19
Figure 15: Wireframe 3..................................................................................................................................... 20
Figure 16: Wireframe 4..................................................................................................................................... 21
Figure 17: Mockup............................................................................................................................................ 22
1. Undertake a software investigation to meet a business need (P5)
1.1. Identify the stakeholders, their roles and interests in the case study
A stakeholder is a party who has an interest in a firm and may either influence or be
influenced by it. A typical corporation's key stakeholders are its investors, workers,
customers, and suppliers.
However, as the focus on corporate social responsibility has grown, the notion has been
expanded to encompass communities, governments, and trade groups.

Figure 1: The stakeholders

There are two types of stakeholders: internal or external these types is described belows:
 Internal stakeholders are those who have a direct interest in a firm, such as
employment, ownership, or investment.
Business analysts is the guy who connect between customers and the technical team of
software developers in the project. The business analyst discussed with the customers of the
project, evaluated the program, defined specifications, reported,explained the project to the
technical team and cooperated with them during the process of development.
A Business Analyst job description typically includes:
 Creating a detailed business analysis, outlining problems, opportunities andsolutions
for a business.
 Budgeting and forecasting.
 Planning and monitoring.
 Financial modelling.
 Variance Analysis.
 Pricing
 Reporting
 Defining business requirements and reporting them back to stakeholders.
In SDLC, the business analyst will provide various services:
 Support for business cases.
 Perform high-level feasibility studies.
 Collection of requirements.
 Design and/or analysis of school test cases.
 Managing change requests.
  Tracking requirements during implementation.
 Management of project scope.
 Approval, integration and deployment.
System Analysis
Design an online healthcare system with the following list:
 Interfaces with online healthcare service system.
 Data models and system performance.
 Process models and user interface.
 User Experience.
Infrastructure analysis
Health Connect's online healthcare system must ensure standards, stability, and support the
company for the next 5 years. Not only that, the system must be easy to maintain and easy
to upgrade.
Project Manager
Manage the entire Health Connect software development project to ensure quality,
timeliness, and compliance with budgets
Programmers
As a team directly execute software such as code config functions and database.
External stakeholders are individuals who do not directly work for a company but are
influenced in some way by its activities and consequences. External stakeholders include
suppliers, creditors, and public organizations.
Health Connect’s Owners
Health Connect is a southern California based company. Health Connect is the brainchild of
three medical industry entrepreneurs: Hippocrates, Elizabeth Blackwell, Frederick Banting. It
is the network chief who is responsible for overseeing all of the operations. They manage all
system work, staff acts, and other system activities. They are responsible for having the
workstations installed and handled. They require that all customer, staff, products and
services records are accessed as a secure login system.

Figure 2: Types of stakeholders

1.2. FRs and NFRs
What is a Functional Requirement?
A functional requirement defines a program or a component of a program in software
engineering. This specifies the functions that a software is supposed to carry out. A function
is nothing more than its inputs, actions, and outputs. This might be a measurement, data
manipulation, business procedure, user interaction, or any other aspect that defines what a
program is likely to perform.
Functional software requires assistance in capturing the system's desired behavior. This
behavior can be expressed by functions, facilities, or tasks, or it can be represented by which
program is required to execute.

What is Non-Functional Requirement?

A nonfunctional requirement specifies a software system's quality attribute. They are a set
of standards that are used to determine the specific activity of a system. How rapidly, for
example, does the page load?
A non-functional requirement for guaranteeing the overall reliability and performance of the
operating system. Non-functional criteria that are not met can lead to systems that do not
fulfill user needs.
Non-functional Requirements allow you to impose constraints or requirements on system
design via the various agile backlogs. For example, if the number of concurrent users is more
than 10,000, the site will load in 3 seconds. Non-functional needs have been defined.

1.3. Compare Functional vs Non Functional Requirements:

Figure 3: Compare Functional vs Non Functional Requirement

1.4. FRs and NFRs in Health Connect
Functional Requirements:
 User Registration and Authentication: The website should allow users to create
accounts, log in, and authenticate their identity securely. It should also provide
options for password recovery and multi-factor authentication for added security.
 Appointment Scheduling: Users should be able to schedule appointments with
healthcare providers, view available time slots, and receive confirmation
notifications. The system should also support rescheduling and cancellations.
 Electronic Health Records (EHR) Access: Patients should be able to access their
electronic health records, and view medical history, test results, and medication
prescriptions securely. Healthcare providers should have tools for updating and
maintaining these records.
 Telehealth Services: The website should enable video consultations and telehealth
services, allowing users to connect with healthcare professionals remotely for advice,
diagnosis, and treatment.
 Health Information and Education: Provide access to reliable health information,
articles, and resources to educate users about various medical conditions and
treatment options.
 Prescription Refills: Allow users to request prescription refills and facilitate
communication between patients and healthcare providers for prescription
management.
 Billing and Payment Processing: Users should be able to view and pay medical bills
online, with secure payment processing and the ability to check insurance coverage
and claim status.
 Search and Filter: The website should have a robust search and filter functionality to
help users find healthcare providers, specialists, and services based on location,
specialty, and other criteria.

Non-Functional Requirements:
 Security and Privacy: Ensure the highest level of data security and compliance with
privacy regulations such as HIPAA, GDPR, and relevant industry standards to protect
users' personal and medical information.
 Performance and Scalability: The website should be responsive, load quickly, and
handle a large number of concurrent users, especially during peak times. It should
scale easily to accommodate growing user demand.
 Reliability and Availability: Ensure that the website is available 24/7 with minimal
downtime for maintenance or upgrades. Implement redundancy and failover
mechanisms to prevent service disruptions.
 Usability and Accessibility: Design the website to be user-friendly, with clear
navigation, accessible for individuals with disabilities, and responsive across various
devices and screen sizes.
 Compliance and Regulations: Ensure adherence to relevant healthcare regulations,
including healthcare data standards, interoperability, and accessibility guidelines.
 Data Backup and Recovery: Implement regular data backups and a robust disaster
recovery plan to protect against data loss and ensure data integrity.
 Integration with Existing Systems: The website should integrate seamlessly with
existing healthcare systems, such as hospital management software, laboratory
systems, and insurance platforms.
  Performance Monitoring: Continuously monitor website performance, user
feedback, and error logs to identify and address issues promptly.
 Load Testing: Conduct load testing to determine the website's capacity to handle
peak loads and optimize performance accordingly.
 Mobile Responsiveness: Ensure that the website is mobile-friendly, with a responsive
design and a dedicated mobile app to cater to users accessing the platform from
smartphones and tablets.

2. Discuss the technique(s) you would use to obtain the requirements

2.1. JAD
JAD (Joint Application Development) is a way of including the client or end user in the design
and development of an application through a series of collaborative workshops known as
JAD sessions.
JAD is a software development methodology that improves stakeholder collaboration
throughout software development cycles. Its life cycle has been used in domains of dynamic
software development. While developing a new information system for any company or firm,
it collects business and system needs.

Figure 4: JAD
Phases of JAD Model:
Now that you've learned about the JAD idea, it's time to learn about its stages and how the
model's design and development strategy works:
 Defining Specific Objectives: In collaboration with stakeholders, the facilitator
establishes all goals and a list of items, which are then disseminated to other
developers and participants to comprehend and review. This purpose includes
aspects such as the scope of the proposed system, its potential conclusion, the
technological standards that must be met, and so on.
 Session preparation: The facilitator is exclusively responsible for this preparation,
which includes gathering all required data and forwarding it to other members in
advance. To have a deeper understanding, effort has been done to learn more about
the device requirements and to collect all of the necessary implementation
knowledge.
 Session Conduct: The facilitator is in charge of identifying the issues that need to be
resolved in order for the system to be error-free. The facilitator will take part in this
discussion but will have no influence over the information.
  Documentation: After the product has been developed, reports and written papers
are provided to the meeting so that it may be accepted by stakeholders and
customers through the meeting.
Benefit of using JAD Model is list below:
 Improved delivery time: The JAD model requires less time and is more efficient than
other traditional approaches to build a product.
 Cost reduction: Efficient consultation of the specifications and facts with company
leaders and stakeholders will allow for less work to implement the program, and
therefore less expense for the full implementation phase.
 Improved comprehension: As the entire criterion is examined by business managers,
a thorough selection of engineers and team leaders who can successfully interact
with one other often helps to better understand the product development.
 Improved Quality: Because all of the project's key decision-makers and stakeholders
are involved in project development, there is less chance of error, and therefore the
product's quality is better and more dependable.
When to use JAD?
Project Types - JAD has been used effectively on a variety of projects, including the following:
 New systems.
 Enhancements to existing systems.
 System conversions.
 Purchase of a system.
Project Characteristics - Not every project, however, is a suitable fit for JAD. A suitable project
will have at least some of the following characteristics:
 Involves many groups of users whose responsibilities cross traditional department or
division boundaries.
 Is considered critical to the future success of the organization.
 Involves willing users.
 Is a first-time project for the organization.
 Has a troubled project history or relationship between the systems and user
organizations.
While the traits listed above characterize a solid JAD candidate project, not all of them should
be present in your initial JAD projects. As the development team and the customer get more
comfortable with the JAD technique, more complicated projects can be undertaken.
2.2. Story mapping
Story mapping is both a visual approach for understanding how a user could utilize a function
and a method of decomposition for thinking about how to breakdown a notion sequentially.
The visual component assists the team in understanding the customer experience by
envisioning the customer procedure. This motivates the team to explore aspects of what the
consumer finds valuable.
The deconstruction section assists the team in considering a number of options that reflect
bits of work (e.g., epics and user stories) on how to create the function progressively in order
to collect the most customer feedback. This helps to establish the idea's validity while also
ensuring that the concept is constructed in such a way that it provides the best customer
experience possible.

Figure 5: Story mapping

Story Mapping is a technique for bridging the gap between a concept and the incremental
labor that lies ahead. It's a terrific method to break down a concept into a series of distinct
user stories. What are some other advantages of narrative mapping?
 It shifts the focus away from functionality and onto the consumer experience.
 It gives a large picture and end-to-end view of the work that has to be done.
 It's a tool for breaking down a concept into many user stories.
 It asks the team to select the work that has the most customer value and where you
may desire the most client feedback.
 It advocates for just eliminating one increment of work at a time, recognizing that
input from the present increment will help shape subsequent increments
The beautiful thing about narrative mapping is that it can be used at any point in the
product's life cycle.
 Creating an MVP? A narrative map is an excellent tool for determining the bare
minimum of functionality required to test your concept. It will keep you from
"forgetting" about important aspects of the user experience that you may otherwise
ignore.
 Are you attempting to improve on version 1.0? A narrative map may help your team
have excellent talks about what will have the largest impact on your users by clearly
displaying all of the various upgrades you might implement.
  Are you in charge of a strong, ongoing business? Story mapping may help you control
the backlog by providing context for each item and requiring prioritizing and grouping
with a big-picture view, as well as highlighting gaps you would not have spotted
otherwise.
 Are you looking to expand your product line with a new product extension? A
narrative map will show you what you already have and what elements are required
to make the new feature work as well as your present offering.

3. Use appropriate software analysis tools/techniques to carry out a software investigation

and create supporting documentation (P6)
3.1. Context Diagram

Figure 6: Context Diagram

3.2. Data Flow Diagram
Data flow diagrams are used to graphically describe data flow inside a corporate information
system. DFD specifies the procedures that take place in a framework for transporting data
from input to file storage and creating reports.
The data flow diagrams may be divided into logical and physical ones. The logical data flow
diagram depicts the movement of data through a system in order to fulfill certain business
functionality. The conceptual data flow implementation is defined by the data flow diagram.

3.3. ERD
The Entity Relationship Diagram (ERD), also known as the ER Diagram or the ER model, is a
sort of structural diagram used in database architecture. An ERD comprises several symbols
and connections that depict two crucial pieces of information: the principal entities inside
the system scope, as well as the inter-relationships between these entities.
That is why we require ERD for Health Connect Software developers to comprehend things
more easily and simply for upgrades, debugging, and maintenance.
Health Connect Online Music System ERD:

Figure 7: ERD for Health Connect

Since the team had already analyzed and produced DFD, we created ERD for data storage for
Health Connect Online healthcare service systems, which contained four tables:
 Healthcare service DB: This database stores the service name, performer, and price.
 Purchase DB: This database stores the purchase ID, service pack ID, Customer ID, and
purchase date of the payment process.
 Customer DB: This database stores usernames and passwords for the Health Connect
website's login feature.
 Customer Infor: This database stores personal information on users in order to learn
more about their credentials.
3.4. Flowchart
3.4.1. Search in web

Figure 8: Search in web

Health Connect has an online search tool. When visitors visit the website, they will enter
the term to search for in the search box to begin looking for the healthcare. The
algorithm will recommend the most suitable medical services based on three criteria:
name, healthcare staff, and price. The search results show when the consumer has set
the filter criteria. If it matches what the customer is looking for then the function will be
terminated. However, if this is not the case, users will begin inputting a new term to
continue their search.
 3.4.2. Purchase

Figure 9: Purchase
After buyers look for a suitable service, they want to register from Health Connect Web. The system
will inquire if the client has an account, and if not, the consumer must complete the appropriate
registration requirements before moving on to the next phase. If the consumer already has an
account, he will use that mode of payment. The system will then return the payment details and
prompt the consumer to approve whether or not the payment should be accepted. If the customer
accepts, the system will begin to arrange an online meeting to understand the customer's medical
condition better and make an appointment for the customer to come to the hospital for convenient
examination and customer care according to the service they have purchased; otherwise, the system
will display an error message and return to the payment page.
4. Explain how user and software requirements have been addressed (P7)
4.1. Use Case Diagram

Figure 10: Use Case Diagram for the whole system

4.2. Use Case specification

4.2.1. View/Update detail

Figure 11: View/Update detail

4.2.2. Update service diagram
 Admin

Figure 12: Update service diagram

4.3. Wireframe
A wireframe website, also known as a schematic page or computer diagram, is a visual guide
that describes a website's architectural framework. Wireframes are created to organize
pieces in order to better serve a given goal. Typically, a corporate objective and an original
concept communicate the aim. The wireframe depicts the page layout or organization of the
website's content, including interface components and navigation mechanisms, and how
they interact.
Because the major emphasis is on functionality, activities, and material priorities, the
wireframe typically lacks typographic design, color, or graphics. In other words, it focuses on
what a screen accomplishes rather than how it appears. Wireframes can be whiteboard
pencil sketches or drawings, or they can be created using a wide range of free and paid tools.
Wireframes are often created by market analysts, customer interface designers, developers,
graphic designers, and others with experience in interaction design, information
architecture, and consumer analysis.
Wireframe focus on:
 The number of possible functions.
 The relative importance of information and functions.
 The criteria for presenting specific types of information.
 The impact of various circumstances on the presentation.
Wireframe of the Health Connect project:

Figure 13: Wireframe 1

Figure 14: Wireframe 2
Figure 15: Wireframe 3
E
Figure 16: Wireframe 4
4.4. Mockup
A mockup, also known as a mock-up, is a full-size or scale model of an idea or product that is
used in manufacturing and construction for training, presentation, concept review,
promotion, and other purposes. A mockup is a prototype since it has at least some of the
functionality of a system and enables for the testing of a concept. Mock-ups are mostly used
by designers to get user feedback. Mock-ups address the idea encapsulated in a famous
oneliner engineering: You can correct it now with an eraser on the drawing board, or you can
fix it later on the construction site with a sledgehammer.

Figure 17: Mockup

References
Stakeholder. (2021). Retrieved from https://www.investopedia.com/terms/s/stakeholder.asp