Higher Nationals in Computing
UNIT 9: SOFTWARE DEVELOPMENT LIFE CYCLES
ASSIGNMENT 1
Assessor name: VO NGOC MAI
Learner’s name: NGUYEN GIA HUY
ID: GCS200801
Class: GCS0905C
Subject code: 1631
Assignment due: Assignment submitted:
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
software development life cycle (1631) - Assignment 2 ( asm2 ) - PASS, Assignments of Software Development
software development life cycle (1631) - Assignment 2 ( asm2 ) - PASS - SDLC
Typology: Assignments
2021/2022
1 / 34
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download software development life cycle (1631) - Assignment 2 ( asm2 ) - PASS and more Assignments Software Development in PDF only on Docsity!
Higher Nationals in Computing
UNIT 9: SOFTWARE DEVELOPMENT LIFE CYCLES
ASSIGNMENT 1
Assessor name: VO NGOC MAI
Learner’s name: NGUYEN GIA HUY
ID: GCS
Class: GCS0905C
Subject code: 1631
Assignment due: Assignment submitted:
ASSIGNMENT 0 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 0 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name NGUYEN GIA HUY Student ID GCS Class GCS0905C Assessor name 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 HUY Grading grid P5 P6 P7 M3 M4 M5 M6 D3 D
Assignment Brief 02 (RQF)
Higher National Certificate/Diploma in Business
Student Name/ID Number: NGUYEN GIA HUY / GCS Unit Number and Title: Unit 09: Software Development Life Cycle Academic Year: 2022 Unit Assessor: Assignment Title: Undertake a software development life cycle Issue Date: 07/12/ Submission Date: Internal Verifier Name: Date: Submission Format: Format: The submission is in the form of 1 document. You must use the Times font with 12pt size , turn on page numbering ; set line spacing to 1. and margins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation and references must follow the Harvard referencing style. Word limit : 3000 words (excluding figures and references). Submissions that exceed this limit will be rejected. Submission: You must submit the assignment by the due date and follow the submission method specified by the Tutor. The submission form is soft copy , which is to be uploaded to the following URL: http://cms.greenwich.edu.vn. Note: Your assignment must be your own work, and not copied by or from another student or from other sources, such as book etc. If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference the sources, using the Harvard style. Make sure that you know how to reference properly and that you understand the plagiarism guidelines. Plagiarism is a very serious offence , which will result in a failing grade. Unit Learning Outcomes:
LO3 Undertake a software development lifecycle. LO4 Discuss the suitability of software behavioral design techniques. Assignment Brief and Guidance: Tasks At this stage, you have convinced Tune Source to select your project for development. Complete the following tasks to analyze and design the software. Task 1 – Analysis (1)
- (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. [MV]
- Intro purpose of this section
- Introduction of requirement definition, FR, NFR and more details
- Present the discussion about relationships between the FRs and NFRs
- List out stakeholders who can provide requirements, their roles and their interests in Tune Source project
- Present the Requirement Definition (with explaining its need/ purpose) of TS project. Clearly indicate which stakeholder(s) provide what requirements. Propose some NFRs for TS project and explain why.
- (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. [MV]
- Intro purpose of this section
- Describe 5 requirement gathering techniques: Interviews, Join Application Development, Questionnaires, Document Analysis, Observation (description, steps, pros & cons, ..)
- Apply to TS: select ones that suitable for Tune Source and explain why
- Add at least 2 Interview notes for TS
- (M3) Discuss how you would trace these requirements throughout the project. [MV]
- Must have a Traceability Matrix for TS
Differentiate between FSM And extended FSM using the case study.
- (D4) Discuss how the data-driven approach improves the reliability and effectiveness of software. Task 4 – Software quality management
- (M4.a) Discuss two software quality attributes that are applicable to the project. [MV]
- Some attributes such as availability, interoperability, correctness, reliability, learnability, robustness, maintainability, readability, extensibility, testability, ...
- (M4.b) Discuss two quality assurance techniques that can help improve the software quality in the project. [MV] Some techniques such as Black Box testing techniques?
- Boundary Value Analysis.
- Equivalence partitioning.
- State Transition Testing.
- Decision Table Testing.
- Graph-Based Testing.
- Error Guessing Technique.
- (D3) Discuss how the design techniques and approaches that you have used can help improve the software quality. [MV] This section is about Test design technique (with Test Case Design examples)
Learning Outcomes and Assessment Criteria Pass Merit Distinction LO3 Undertake a software development lifecycle D 3 Critically evaluate how the use of the function design paradigm in the software development lifecycle can improve software quality. P5 Undertake a software investigation to meet a business need. P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation. M3 Analyse how Software requirements can be traced throughout the software lifecycle. M4 Discuss two approaches to improving software quality. LO4 Discuss the suitability of software behavioural design techniques D4 Present justifications of how data driven software can improve the reliability and effectiveness of software. P7 Explain how user and software requirements have been addressed. M5 Suggest two software behavioural specification methods and illustrate their use with an example. M6 Differentiate between a finite state machine (FSM) and an extended- FSM, providing an application for both.
- Unit 9: Software Development Life Cycles ASSIGNMENT - P5. Undertake a software investigation to meet a business need............................................ - A. Identify the stakeholders, their roles and interests in the case study.
- Introduction of requirement definition of the project.
- 1.1. What is the Requirement?
- 1.2. Functional Requirements (FR):........................................................................................................ - 1.2.1. What is a Functional Requirement? - 1.2.2. What should be included in the Functional Requirements Document? - 1.2.3. What are the advantages of Functional Requirements? - 1.2.4. Types of Functional Requirements
- 1.3. Non Functional Requirements (NFR): - 1.3.1. What is a Functional Requirement? - 1.3.2. What are the advantages of Non-functional Requirements? - 1.3.3. Types of Non-functional Requirement:
- 1.4. Functional vs Non Functional Requirements
- Present the discussion about relationships between the FRs and NFRs:
- project: 3. List out stakeholders who can provide requirements, their roles and their interests in Tune Source
- which stakeholder(s) provide what requirements. Propose some NFRs for TS project and explain why: 4. Present the Requirement Definition (explaining its need/ purpose) of the TS project. Clearly indicate
- B. Discuss the technique(s) you would use to obtain the requirements.
- Questionnaires, Document Analysis, Observation 1. Describe 5 requirement gathering techniques: Interviews, Join Application Development,
- 1.1. Interviews
- 1.2. Observation
- 1.3. Prototyping
- 1.4. Survey/Questionnaire
- 1.5. Focus Group
- 1.6. Document Analysis/Review
- 1.7. Stakeholder Analysis
- and create supporting documentation. P6. Use appropriate software analysis tools/techniques to carry out a software investigation
- Requirements Modelling:
- Apply to TS:
- 2 .1. ERD for Tune Source:
- 2 .2. DFD for Tune Source: - 2 .2.1. Tune Source DFD:
- 2.3. Flowchart for Tune Source: - 2 .3.1. Search flowchart: - 2 .3.2. Buy flowchart:..................................................................................................................................
- 2 .4. Pseudocode for Tune Source:.................................................................................................................
- P7. Explain how user and software requirements have been addressed.
- Questionnaires, Document Analysis, Observation 1. Describe 5 requirement gathering techniques: Interviews, Join Application Development,
- Details of use case diagram:
- Apply to TS:
- 2.1. Major use case:
- 2.2.1. Buy Function
- 2.2.2. Search Function
- 2.2.3. Login Function..................................................................................................................................
- 2.2.4. Register Function
P5. Undertake a software investigation to meet a business need A. Identify the stakeholders, their roles and interests in the case study.
- Introduction of requirement definition of the project. 1.1. What is the Requirement? An individual physical or functional requirement is something that product development and process improvement attempt to address through a particular design, product, or procedure. It is frequently utilised in formal engineering design processes like systems engineering, software engineering, or enterprise engineering. It is a broad concept that can refer to any necessary (or occasionally desired) feature, ability, quality, or characteristic of a system in order for it to be valuable and practical for a client, business, internal user, or other stakeholders. 1.2. Functional Requirements (FR): 1.2.1. What is a Functional Requirement?
- handling of historical data
- Regulations and Legal Requirements 1.3. Non Functional Requirements (NFR): 1.3.1. What is a Functional Requirement? Non-Functional Requirement (NFR) describes a software system’s quality aspect. They assess the software system according to non-functional criteria such as responsiveness, usability, security, portability, and other criteria essential to the software system’s success. The non-functional requirement “how quickly does the page load?” is an example. Systems that do not satisfy user demands might come from not meeting non-functional criteria. 1.3.2. What are the advantages of Non-functional Requirements?
- They make that the software program complies with all applicable laws and regulations.
- They detail the software’s quality characteristics.
- They ensure the software system is reliable, available, performant, and scalable.
- They contribute to the development of the software system’s security policy.
- They guarantee a positive user experience, make it simple to use the program, and keep costs down. 1.3.3. Types of Non-functional Requirement: Types of Non-functional Requirements:
- Scalability
- Reliability
- Regulatory
- Maintainability
- Serviceability
- Utility
- Security
- Manageability
- Data integrity
- Capacity
- Regulatory
- Availability
- Usability
- Interoperability
- Environmental 1.4. Functional vs Non Functional Requirements Here, are key differences between Functional and Non-functional requirements in Software Parameters Functional Requirement Non-Functional Requirement What it is Verb Attributes Requirement It is mandatory It is non-mandatory Capturing type It is captured in use case. It is captured as a quality attribute. End result Product feature Product properties Capturing Easy to capture Hard to capture Objective Helps you verify the functionality of the software. Helps you to verify the performance of the software. Area of focus Focus on user requirement Concentrates on the user’s expectation. Documentation Describe what the product does Describes how the product works Type of Testing Functional Testing like System, Integration, End to End, API testing, etc. Non-Functional Testing like Performance, Stress, Usability, Security testing, etc. Test Execution Test Execution is done before non- functional testing. After the functional testing Product Info Product Features Product Properties
Documentation Describe what the product does Describes how the product works Type of Testing Functional Testing like System, Integration, End to End, API testing, etc. Non-Functional Testing like Performance, Stress, Usability, Security testing, etc. Test Execution Test Execution is done before non-functional testing After the functional testing Product Info Product Features Product Properties
- List out stakeholders who can provide requirements, their roles and their interests in Tune Source project: 3.1. Identify the stakeholders, their roles, and interests in the case study Definition of stakeholder A stakeholder is any person, group, or organisation whose interests are affected by the success or failure of a project or commercial endeavour. They may be inside or outside the company funding the initiative, but they all have a stake in its success. Stakeholders are crucial since their decisions can positively or negatively impact the project. There are additional crucial or essential stakeholders whose backing is necessary for the project to proceed. 3.2. Stakeholder role with interest in Tune Source project. STAKEHOLDER ROLES INTEREST Nguyen Gia Huy Project Manager Project managers lead in planning, executing, monitoring, controlling and closing projects. Here is a look at the project manager's role, responsibilities, relevant certifications, expected salaries, and job- seeking tips. Users Customers Customer is a role who uses Tune Source services to play music and buy increase the company’s income. Xuan Quang, Co-Founders of Tune The co-founders will be in charge of developing the project and submitting ideas, as well as managing the
Quang Duy Source budget and spending. The IT department at Tune Source Management, maintenance, And monitoring of the website Become experienced with Internet technology as it has worked with the ISP to maintain the site Minh Duc, Assistant Vice President, Marketing Project Sponsor The project sponsor will be responsible for the project's overall success, including the selection of the project manager and team, establishing success criteria, and the practical completion of the project. 3.3. Stakeholder requirements STAKEHOLDER REQUIREMENT PROVIDE Nguyen Gia Huy Carry the project; help the team develop software for the requirements specified Users Consumers will have the option to look for and buy digital music downloads. Xuan Quang, Quang Duy Co-Founders need to bring the system to the marketplace as soon as possible The IT department at Tune Source Increase revenue by enabling the sale of no-copyright music downloads to consumers through kiosks in their stores and online through their website. Minh Duc, Assistant Vice President, Marketing Management, maintenance, and direct
- Present the Requirement Definition (explaining its need/ purpose) of the TS project. Clearly indicate which stakeholder(s) provide what requirements. Propose some NFRs for TS project and explain why: FUNCTIONAL REQUIREMENTS DESCRIPTION EXAMPLE
FUNCTIONAL REQUIREMENTS DESCRIPTION Security Security on a user's database should include a firewall to prevent unauthorised access Capacity Make sure that the capacity of the system is enough to accommodate when many people visit at the same time; users can adjust and save settings based on their preferences Compatibility The system works efficiently in a variety of environments. Users can access the website on many devices such as phones, tablets, laptops... Reliability Technology that is highly reliable functions with the same or similar efficacy after extensive use B. Discuss the technique(s) you would use to obtain the requirements.
- Describe 5 requirement gathering techniques: Interviews, Join Application Development, Questionnaires, Document Analysis, Observation 1.1. Interviews ❖ Description: This is the most typical strategy for eliciting requirements. Strong connections between business analysts and stakeholders should be built via the use of interview techniques. In this strategy, the interviewer asks questions of stakeholders in order to gather information. The most prevalent strategy is one-on-one interviews. ❖ Benefits:
- Easy correction of speech: In an interview, it is simple to clear up any misunderstandings and errors. the interviewer and interviewee were present in person before the interview board.
- Development of relationship: An interview can be used to establish a relationship between the interviewer and the interviewee. It improves the parties' understanding and cooperation of one another.
- Selection of suitable candidate: Interviews are a good way to choose qualified applicants since they reveal a lot about the applicant.
- Collection of primary information: Interviews can assist in gathering fresh, new, and primary data as required.
- Sufficient informationThe interviewing technique can be used to get enough data. because the interviewer is free to ask the interviewee any question.
- Timesaving: Interviews can help you choose the best applicant faster. With the interview, contact may be established in a remarkably short amount of time. Less expensive: Compared to other communication methods, it is more affordable. It is an efficient, quick, and inexpensive way of communication.
- Increasing knowledge: Any interview broadens both the interviewer's and the interviewee's knowledge. They may discuss and debate various points of view.
- Explore cause behind the problem: Executives in the corporate world have a variety of issues to address. You can utilize the interview approach to investigate or ascertain the true causes of the issue.
- In depth analysis: Planned interviews allow for the collection of specific information that is necessary for a problem's thorough study. Interviews are a good method for assessing or analyzing abstract elements such as attitudes, sentiments, opinions, etc.
- Solving labor problems: The industries frequently experience labor unrest and other types of problems. Human resource managers may utilize the interview to uncover the true reasons behind labor disputes.
- Flexible: Possibility is one of the main benefits of an interview. It can be phrased in a variety of ways depending on the circumstances. ❖ Drawbacks:
- Incomplete process: A suitable applicant cannot be chosen only based on an interview. The interview is less significant than the written exam.