1. Trang chủ
  2. » Luận Văn - Báo Cáo

unit 09 software development life cycles

44 0 0
Tài liệu được quét OCR, nội dung có thể không chính xác
Tài liệu đã được kiểm tra trùng lặp

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Tiêu đề Software Development Life Cycles
Tác giả Hoang Van Phat
Người hướng dẫn Vo Ngoc Mai
Trường học University of Greenwich
Chuyên ngành Computing
Thể loại Assignment
Năm xuất bản 2020-2021
Định dạng
Số trang 44
Dung lượng 6,81 MB

Nội dung

[f you do not, you definitely get failed Unit Learning Outcomes: LO3 Undertake a software development lifecycle LO4 Discuss the suitability of software behavioural design techniques

Trang 1

'ÿ GREENWICH SBT EC

Higher Nationals in Computing

UNIT 09: SOFTWARE DEVELOPMENT LIFE

CYCLES ASSIGNMENT 2

Assessor name: VO NGOC MAI

Learner’s name: HOANG VAN PHAT

Trang 2

Yas? GREENWICH “BTEC

° nace win LSID, oon

Qualification BTEC Level 5 HND Diploma in Computing

Unit number Unit 9: Software Development Life Cycle

Assignment title Undertake a Software Development Lifecycle

Academic Year 2020 — 2021

Unit Tutor Vo Ngoc Mai

Issue date Submission date | 22/12/2020

IV name and date

Submission Format:

Format: The submission is in the form of 1 document

You must use font Calibri size 12, set number of the pages and use multiple line spacing at 1.3 Margins must be: left: 1.25 cm; right: I cm; top: I cm and bottom: I cm The reference follows Harvard referencing system

Submission Students are compulsory to submit the assignment in due date and in a way requested by the Tutors The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/ Note: The Assignment must be your own work, and not copied by or from another student or from books etc If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style Make sure that you know how to reference properly, and that understand the guidelines on plagiarism [f you do not, you definitely get failed

Unit Learning Outcomes:

LO3 Undertake a software development lifecycle

LO4 Discuss the suitability of software behavioural design techniques

Assignment Brief and Guidance:

Task1

Now your team had been accepted to create the Software to Tune Source As a member of a

development team, your task now is to produce the requirements for Tune Source You also need to specify the technique(s) or processes you used in order to get these requirements

Page 2

Trang 3

Yas? GREENWICH “BT EC

° nace win LSID, oon

Trang 4

Submission date 22/12/2020 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name HOANG VAN PHAT Student ID GCS 190614

Class GCS0805_PPT Assessor name VO NGOC MAI

Trang 5

‘7 GREENWICH “BT EC

e

ance wes [GIG seat

Summative Feedback: Resubmission Feedback:

Grade: Assessor Signature: Date:

Page 5

Trang 7

LO3 Undertake a software development lifecycle

LO4 Discuss the suitability of software behavioural design techniques

e (P5.a) Identify the stakeholders, theirs roles and interests in the case study

Review the requirement definition of the project Clearly indicate which stakeholder(s) provide what requirements

Discuss the relationships between the FRs and NFRs

e =©(P5.b) Discuss the technique(s) you would use to obtain the requirements

If needed, you may state suitable additional assumptions about the project in order to justify the technique(s) that you choose

® (M3) Discuss how you would trace these requirements throughout the project

Based on the analysis result, discuss how you would conduct the design phase:

e (P7) Discuss how the user and software requirements are addressed in the design phase

Page 7

Trang 8

42 UNIVERSITY

ay °

GREENWICH “BT EC ° nace win LSID, oon

e¢ (M5) Discuss how flow chart and pseudocode are used to specify the software behaviour

¢ (M6) Discuss how UML state machine can be used to specify the software behaviour Differentiate between FSM And extended FSM using the case study

e (D4) Discuss how the data-driven approach improves the reliability and effectiveness of software Task 4 — Software quality management

e =(M4.a) Discuss two software quality attributes that are applicable to the project

e (M4.b) Discuss two quality assurance techniques that can help improve the software quality in the project

e (D3) Discuss how the design techniques and approaches that you have used can help improve the software quality

Page 8

Trang 9

42 UNIVERSITY Yas? GREENWICH

nace win LSID, oon ‘BTEC

LO3 Undertake a software development lifecycle D3 Critically evaluate

how the use of the function design paradigm

in the software development lifecycle can improve software quality

M4 Discuss two approaches to improving software quality

design techniques

LO4 Discuss the suitability of software behavioural D4 Present justifications

of how data driven software can improve the reliability and effectiveness of software

M6 Differentiate between

a finite state machine (FSM) and an extended- FSM, providing an application for both

Page 9

Trang 10

đà UNIVERSITY

GREENWICH “BT E

° pmax ith 8g —

Table of Contents

Unit 09: Software Development Life Cycles ASSIGNMENT 2

P5 Undertake a softwareinvestigation to meet abusiness need

(P5.a) Identify the stakeholders, theirs roles and interests in the case stUd|y -.c Sen

1 Introduce the stakeholders

2 Identify the stakeholders

2.1 Definition the stakeholders, their roles and interests

2.2 Roles of the stakeholders

2.3 Benefits of the stakeholders

1 Introduce to the technique

2 Five requirement gathering techniques

1 Introduction to software analysis tools

1.1 Benefits of Software Analysis Tools

1.2 UML (Unified Modeling Language)

2 Structured analysis and design techniques

2.1 DFD

2.1.1 DFD Iv0 of Tune Source project

2.1.2 DFD v1 of the Tune Source project

2.2 _ ERD of the Tune Source project

2.3 Flowchart of the Tune Source project

Trang 11

Yas? GREENWICH “BT EC

° nace win LSID, oon

2.4 Pseudocode 35 P7 Explain how user and software requirements have been addressed :eccscsecseeseceeceeceeceeeeeeeeeeseeeees 36

1 Introduction about user and software requirements 36 1.1 User requirements 36 1.2 Software requirements 36

2 Identifying the Major Use Cases 37

3 Elaborating on the Use Cases 40 3.1 Register Use Cases 40 3.2 Music Use Cases 41 REFERENCES 43

Page 11

Trang 12

Yas? GREENWICH “BTEC

° pmax ith 8g —

Answer

P5 Undertake a softwareinvestigation to meet abusiness need

(P5.a) Identify the stakeholders, theirs roles and interests in the case study

1 Introduce the stakeholders

In your work or volunteering — or other areas of your life — you may have noticed that some individuals and groups have quite a lot of power in how your organisation is run or how services are provided Power means the potential to influence but whether people use this power will depend on what interest they have in influencing the organisation

Some people have little power but a lot of interest in how the organisation is run and what it does These individuals or groups could be service users, volunteers and employees, funders, the general public or the media, to name a few These are some of the many stakeholders of an organisation, and they can be very influential in how an organisation meets its mission, how it’s viewed in the

community, whether it receives funding, or how well it provides its services

There are many reasons why it is important not to neglect stakeholders: ensuring that people are consulted can help less powerful groups have a voice in decision making but equally, some groups may decide to campaign against a decision made by staff or trustees These groups may be powerful enough

—or rally enough support — to reverse decisions or to prompt resignations A recent example of this is a community shop in south-west England where the community argued against the management committee’s decisions and all the committee members felt they had to resign

2 Identify the stakeholders

2.1 Definition the stakeholders, their roles and interests

A stakeholder is an individual or group that has a legitimate interest in a company, organization,

or business The Stanford Research Institute defines stakeholders as “those groups without whose support the organization would cease to exist.” Stakeholders can affect or be affected by the actions (or inactions) of a business, and they can exist both within and outside of a business

Page 12

Trang 13

a7 GREENWICH

"1

A stakeholder is either an individual, group or organization who is impacted by the outcome

of a project They have an interest

in the success of the project

+

MANAGER

2.2.Roles of the stakeholders

Direct the Management: The stakeholders can be a part of the board of directors and therefore help in taking actions They can take over certain departments like service, human resources or research and development and manage them for ensuring success They Bring in Money: Stakeholders are the large investors of the company and they can anytime bring in or take out money from the company Their decision shall depend upon the company’s financial performance Therefore they can pressurize the management for financial reports and change tactics if necessary Some stakeholders can even increase or decrease the investment to change the share price in the market and thus make the conditions favorable for them

Help in Decision Making: Major stakeholders are part of the board of directors Therefore they also take decisions along with other board members They have the power to disrupt the decisions as well They and bring n more ideas a threaten the management to obey them The stakeholders also have all the powers to appoint senior-level management Therefore, they are there in all the major decision-making areas They also take decisions regarding liquidations and also acquisitions

Corporate Conscience: Large stakeholders are the major stakeholders of the company and have monitored over all the major activities of the company They can make the company abide by human rights and environmental laws They also monitor the outsourcing activities and may vote against any business decision if it harms the long term goals of the company

Page 13

Trang 14

Roles of Stakeholders

Service Operations &

Monitoring

Deploying the service

2.3.Benefits of the stakeholders

Fewer surprises How many times have you been caught off guard by a stakeholder? A powerful individual, out of the blue, entered your project world and exerted his or her influence in ways that caused rework and additional cost, resulting in team morale issues

More valuable engagement Janet, a project manager in a health insurance company, has never developed a stakeholder management plan Consequently, she has not adequately engaged key stakeholders On the other hand, Ginger, a project manager in the same company, has regularly worked with her project teams to determine when, how, and where the team would engage the stakeholders Guess who was recently promoted

Better understanding of needs Projects are temporary endeavors resulting in a unique product, service, or result Unique means we’re creating something new or modifying existing products and services Certain individuals, teams, and organizations will be impacted Each of these stakeholders has needs The best project managers identify and seek to understand those needs early in the project

Page 14

Trang 15

DAUR ‘BTEC

ey |-/ eo &

Better understanding of concerns Stakeholders also have concerns Ask them and they will tell you about potential events or conditions that may hinder your progress Other stakeholders can explain how the project may impact their roles and responsibilities

Time invested in the right places You may be a hard-working project manager, working late evenings and weekends The question is: Are you working on the right things? With the stakeholder’s input and regular feedback, you can ensure that you are working on things that have the greatest value

to the project

Happier stakeholders Any chance that you’|l make all the stakeholders happy? Probably not However, you will have a much better chance of keeping stakeholders happy and satisfied if they are properly involved in your projects Less stress for your stakeholders translates into less stress for you as the project manager

Improved communication Stakeholder management includes the identification of your

stakeholders and seeking to understand their preferences Armed with this stakeholder information, project managers can develop a better communications plan

Better management of expectations Individuals, groups, or organizations believe that certain things are going to happen in the future, based on gossip, hearsay, and a few facts The winning project managers seek to understand and to shape the stakeholder’s expectations, guarding against costly false expectations

Improved reputation Project managers with stellar reputations relate well to people in their projects Want to advance in your career? Focus on improving your stakeholder management skills

Page 15

Trang 16

49 GREENWICH “BT E C

nace win LSID, oon

2.4 Types of the stakeholders

Internal stakeholders: Internal stakeholders are groups within a business or people who work directly within the business, such as employees, owners, and investors Employees want to earn high wages and keep their jobs Owners are interested in maximizing the profit the business makes Investors are concerned about earning income from their investment

External stakeholders: External stakeholders are groups outside a business or people who are not directly working within the business but are affected in some way from the decisions of the business, such as customers, suppliers, creditors, community, trade unions, and the government The government wants the business to pay taxes, employ more people, follow laws, and truthfully report its financial conditions Customers want the business to produce quality products at reasonable prices Suppliers want the business to continue to buy their products Creditors want to be repaid on time and in full The community has a stake in the business as employers of local people

internal Stakeholders

Suppliers

Society Employees

Government

Company

a Creditors

Customers s* The stakeholders of the Tune Source project

We have tried our best and believe in the viability and viability of this project Because we have carefully calculated and compared with other projects the success and risks of the project “Source Detector” And we are sure that this project can be successful and thrive

The requirement for the user is that this project can be completed and well developed, minimizing risks thoroughly

3 FRs and NFRs

Page 16

Trang 17

or any other specific functionality which defines what function a system is likely to perform Functional Requirements are also called Functional Specification

In software engineering and systems engineering, a Functional Requirement can range from the high-level abstract statement of the sender's necessity to detailed mathematical functional

requirement specifications Functional software requirements help you to capture the intended behaviour of the system

System Behaviour

+ Functional Requirements should include the following things:

se _ Details of operations conducted in every screen

e Data handling logic should be entered into the system

e |t should have descriptions of system reports or other outputs

¢ Complete information about the workflows performed by the system

e It should clearly define who will be allowed to create/modify/delete the data in the system

se How the system will fulfill applicable regulatory and compliance needs should be captured in the functional document

Trang 18

Historical Data management

Legal and Regulatory Requirements

“ Example:

The software automatically validates customers against the ABC Contact Management System

The Sales system should allow users to record customers sales

The background color for all windows in the application will be blue and have a hexadecimal RGB color value of OxQOOOFF

Only Managerial level employees have the right to view revenue data

The software system should be integrated with banking API

The software system should pass Section 508 accessibility requirement

“* Advantages of FRs:

Here, are the pros/advantages of creating a typical functional requirement document-

Helps you to check whether the application is providing all the functionalities that were mentioned in the functional requirement of that application

A functional requirement document helps you to define the functionality of a system or one of its subsystems

Functional requirements along with requirement analysis help identify missing requirements They help clearly define the expected system service and behavior Errors caught in the Functional requirement gathering stage are the cheapest to fix Support user goals, tasks, or activities

“+ FRs of the Tune Source:

e Users can use the subscribe function to prioritize downloads of their favorite music

Page 18

Trang 19

DAUR BTEC

pee ts IG cr =

e When registering an account on the system, email and account confirmation code are sent

to the user's phone number when registering for the first time

e Users log into the system to personalize and download music

e Users can find the name of the track they need in the database

e Brave people can listen to sample music on the system

e Users can shut down the system when under a network attack

e Users can buy gift cards to download free music in a short time when registering an account

on the system

3.2 Definition of NFRs

NON-FUNCTIONAL REQUIREMENT (NFR) specifies the quality attribute of a software system They judge the software system based on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to the success of the software system Example of nonfunctional requirement, “how fast does the website load?” Failing to meet non-functional requirements can result in systems that fail to satisfy user needs

Non-functional Requirements allows you to impose constraints or restrictions on the design of the system across the various agile backlogs

Functional Requirements Non-functional Requirements

Trang 20

nace win LSID, oon ‘BTEC

Here, are some examples of non-functional requirement:

Users must change the initially assigned login password immediately after the first successful login Moreover, the initial should never be reused

Employees never allowed to update their salary information Such attempt should be reported to the security administrator

Every unsuccessful attempt by a user to access an item of data shall be recorded on an audit trail

A website should be capable enough to handle 20 million users with affecting its performance

The software should be portable So moving from one OS to other OS does not create any problem

Privacy of information, the export of restricted technologies, intellectual property rights, etc should be audited

“+ Advantages of NFRs

Benefits/pros of Non-functional testing are:

Page 20

Trang 21

Yas? GREENWICH “BTEC

° pmax ith 8g —

e The nonfunctional requirements ensure the software system follow legal and compliance rules

e They ensure the reliability, availability, and performance of the software system

e They ensure good user experience and ease of operating the software

e They help in formulating security policy of the software system

“+ NFRs of the Tune Source project:

e Tune Source system database can store unlimited songs

¢ The confirmation code or confirmation email sent to the customer cannot be confirmed later than 2 minutes

e All required functions in the Tune Source project are optimized for fastest processing speeds

e Website loading speed will also be optimized as its functions when many users are logged in at the same time

4 Relationships between the functional requirement and non-functional

A functional requirement defines a system or its component whereas a non-functional requirement defines the performance attribute of a software system

Functional requirements along with requirement analysis help identify missing requirements while the advantage of Non-functional requirement is that it helps you to ensure good user experience and ease of operating the software

Functional Requirement is a verb while Non-Functional Requirement is an attribute

Types of Non-functional requirement are Scalability Capacity, Availability, Reliability, Recoverability, Data Integrity, etc whereas transaction corrections, adjustments, and cancellations, Business Rules, Certification Requirements, Reporting Requirements, Administrative functions, Authorization levels, Audit Tracking, External Interfaces, Historical Data management, Legal or Regulatory Requirements are various types of functional requirements

(P5.b) Discuss the technique(s) you did use to obtain the requirements

1 Introduce to the technique

Though there are a plethora of requirements elicitation methods, but there are five key requirements elicitation techniques On the other hand, all of them are needed at some time or the other, but the most famous ones are the needed the most Any business professional cannot do

Page 21

Trang 22

up, the strengths of the team members for the project, the environment of your project, the firm’s requirements and likings, all these factors must be taken into account before zeroing on any elicitation technique Based on these factors decide on the method that works best for your firm and the project

Cases in point, let us discuss the most famous requirements elicitation techniques that specialists need them at any point of the project development, which in turn will provide a pronounced profit on the venture

Page 22

Ngày đăng: 10/08/2024, 22:28

w