1
Software Development Life Cycle
Unit 09: Software Development Life Cycle
ASSIGNMENT 2
Learner’s name: Ly Nguyen
ID: GCS210154
Class: GCS1003A
Subject code: 1631
Assessor name: Vo Ngoc Mai
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 circle(SDLC) assm_2 PASS, Lecture notes of Software Development
Software development life circle Software development life circle Software development life circle
Typology: Lecture notes
2021/2022
1 / 31
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software development life circle(SDLC) assm_2 PASS and more Lecture notes Software Development in PDF only on Docsity!
Software Development Life Cycle
Unit 09: Software Development Life Cycle
ASSIGNMENT 2
Learner’s name: Ly Nguyen
ID: GCS
Class: GCS1003A
Subject code: 1631
Assessor name: Vo Ngoc Mai
Assignment due: Assignment submitted:
ASSIGNMENT 2 BRIEF
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 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: 1 cm; top: 1 cm and bottom: 1 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. If 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:
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.
ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life Cycle Submission date Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Ly Nguyen Student ID GCS Class GCS1003A Assessor name Vo Ngoc Mai 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 Grading grid P5 P6 P7 M3 M4 M5 M6 D3 D
Internal Verifier’s Comments: Signature & Date:
Table of Contents
- 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
- List out stakeholders, roles and their interests on Tune Source project
- stakeholder(s) provide what requirements. Present the Requirement Definition of the project (both FR and NFRs). Clearly indicate which
- Present the discussion about relationships between the FRs and NFRs
- B. Discuss the technique(s) you would use to obtain the requirements......................................
- Interviews.....................................................................................................................................
- Join Application Development
- Questionnaire
- Document Analysis.......................................................................................................................
- Observation..................................................................................................................................
- Conclusion
- A. Identify the stakeholders, their roles, and interests in the case study.
- create supporting documentation. P6. Use appropriate software analysis tools/techniques to carry-out a software investigation and - Introduction about modelling techniques - Structured analysis and design techniques
- P7. Explain how user and software requirements have been addressed. - Use Case Diagram - Use Case Diagram objects - Relationships in Use Case Diagrams - Apply to Tune Source
- References
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
Requirement definition 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 utilized 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. Figure 1 : Requirement definition What is a Functional Requirement? In software engineering, a functional requirement defines a system or its component. It describes the functions a software must perform. A function is nothing but inputs, its behavior, and outputs. It can be a calculation, data manipulation, business process, user interaction, or any other specific functionality which defines what function a system is likely to perform. Functional requirements in software engineering help you to capture the intended behavior of the system. This behavior may be expressed as functions, services or tasks or which system is required to perform. ❖ Example of Functional Requirements Here, are some examples of functional requirement in software engineering:
- 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 0x0000FF.
- 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 Functional Requirement
- 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 for easy project management
- Functional requirement can be expressed in Use Case form or user story as they exhibit externally visible functional behavior. What is Non-Functional Requirement? A non-functional requirement defines the quality attribute of a software system. They represent a set of standards used to judge the specific operation of a system. Example, how fast does the website load? A non-functional requirement is essential to ensure the usability and effectiveness of the entire software system. 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. Example, the site should load in 3 seconds when the number of simultaneous users are > 10000. Description of non-functional requirements is just as critical as a functional requirement. ❖ Examples of Non-functional requirements Here, are some examples of non-functional requirement in software engineering:
- 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.
List out stakeholders, roles and their interests on Tune Source project
Definition of stakeholder A stakeholder is any person, group, or organization whose interests are affected by the success or failure of a project or commercial endeavor. 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. Stakeholder role with interest in Tune Source project. STAKEHOLDER ROLES INTEREST 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. Customers Customer is a role who uses Tune Source services to play music and buy increase the company’s income. Co-Founders of Tune The co-founders will be in charge of developing the project and submitting ideas, as well as managing the Source budget and spending. Management, maintenance, And monitoring of the website Become experienced with Internet technology as it has worked with the ISP to maintain the site 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.
Stakeholder requirement STAKEHOLDER REQUIREMENT PROVIDE Carry the project; help the team develop software for the requirements specified Consumers will have the option to look for and buy digital music downloads. Co-Founders need to bring the system to the marketplace as soon as possible Increase revenue by enabling the sale of no copyright music downloads to consumers through kiosks in their stores and online through their website. Management, maintenance, and direct
Present the Requirement Definition of the project (both FR and NFRs). Clearly
indicate which stakeholder(s) provide what requirements.
FUNCTIONAL REQUIREMENTS DESCRIPTION EXAMPLE
DOWNLOAD Allow customers to download the music they have purchased Customers can download their favorite songs and play them without the internet. Also, you can create an album to add it to. LISTEN Allow consumers to play music online without downloading by connecting to the internet. Customers click the song to listen. When the song ends, the music will be next to a new one SEARCH Allow users to search for songs by entering song- related keywords such as song title, artist name, album name, or a word in the song When a consumer enters a song title or lyric of the song, the system will display the name song REGISTER Allows new users to sign up for a new account to use the Tune Source service. Customers can connect with their registered account and download the copyrighted from Tune Source
Present the discussion about relationships between the FRs and NFRs
The functional requirements and non-functional lay the foundation for a software development project’s success. Functional requirements mentioned specific features to promote the development of software. Non-functional requirements are directly linked to software features. Non-functional requirements represent product criteria from the user’s point of view and describe how a project should be implemented to develop an end-user experience. When you identify the required product features and establish requirements for each, the software development process goes much faster. The project will be affected significantly if the requirements for functional or non-functional have not been determined. Parameters Functional Requirement Non-Functional Requirement What is it? 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 It 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 Expectations. 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
B. Discuss the technique(s) you would use to obtain the requirements
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 with one another.
- Selection of suitable candidates : 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 information interviewing technique can be used to get enough data. because the interviewer is free to ask the interviewee any questions.
- 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 the 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.
- Flexibility : 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.
- Define Session: Define the purpose, scope, and objectives of the JAD session, selecting the JAD team, invite and obtain commitment to attend sessions from the appropriate stakeholders, and schedule the session. It is important to obtain management commitment to support the process and identify the appropriate stakeholders.
- Research Product : Become more familiar with the product or service, gather preliminary information, obtaining any models.
- Prepare : Prepare any visual aids, developing a realistic agenda, training the recorder, and preparing the meeting room.
- Conduct Session : Follow agenda to gather and document the project needs and requirements. It is important to ensure all participants are given equal treatment during the process.
- Draft the Documents : Prepare the formal documents. The information captured in the JAD session is further refined through analysis efforts, open questions or issues discovered through the sessions are resolved, and the final document is returned to stakeholders for review and validation.
Questionnaire
The phrase "questionnaire" refers to the series of questions you are asking an individual. A survey is the process of gathering, analyzing, and interpreting data from a large number of people. It seeks to learn more about a group of individuals. ➢ Benefits:
- Less time is required for the participants to respond.
- You can get more accurate information as compared to interviews. ➢ Drawbacks:
- Follow-up surveys might be required based on the responses provided by participants.
- Questions may not be clear to all the participants.
- Open-ended questions require more analysis.
- All the Stakeholders might not participate in the surveys
Document Analysis
Document analysis/review is a type of qualitative research in which the researcher interprets documents to give voice and meaning to an evaluation issue. Document analysis includes classifying information into themes in the same way that focus group or interview transcripts are evaluated. A rubric may be used to grade or score documents as well. ➢ Benefits:
- Current and future procedures may be compared using existing documentation.
- Existing records can serve as a foundation for future investigation. ➢ Drawbacks:
- Existing papers may not be updated.
- Existing papers may be entirely out of date.
- It is conceivable that resources working on current papers will not be available to provide information.
Observation
The primary goal of the observation session is to comprehend the activity, task, tools utilized, and events carried out by others. The observation plan ensures that all stakeholders are aware of the session's aim, that they agree on the expected outcomes, and that the session satisfies their expectations. You must notify the participants that their performance will not be evaluated. During the session, the observer should record all of the actions and the time it takes others to complete the activity so that he or she can mimic it. Following the session, the BA will go over the results and follow up with the participants. Active and passive observation are both possible. ➢ Benefits:
- The observer will get a practical insight into the work.
- Improvement areas can be easily identified. ➢ Drawbacks:
- Participants might get disturbed.
- Participants' working methods may alter throughout the observation, and the observer may not obtain a clear image.
- Knowledge-based activities cannot be observed.
Conclusion
In this Tune Source project, a survey/questionnaire is used to collect needs since it is simple to collect data from a broad audience, takes less time for users to reply, and provides more reliable information than other strategies. The assumption about the project justifying the techniques that you have chosen: The use of questionnaires in team projects allows for the collection of critical data and information. Furthermore, the team project requires exceptional information in order to produce an excellent study report. Furthermore, if the project requires high-quality data, a well-designed survey or research would be required. Questionnaire processes are the most common and straightforward method of collecting data for research. As a result, a group project may create a survey, distribute it to a large number of people, and then analyze and evaluate the responses.