Download Assignment 2 Software Development Life Circle and more Assignments Software Development in PDF only on Docsity!
ASSIGNMENT 2 SDLC
Qualification BTEC Level 5 HND Diploma in Computing
Unit number and title Unit 09: Software Development Life Cycle
Submission date Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Phan Minh Tien Student ID GCD
Class GCD1001^ Assessor name Tran Trong Minh
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 Tiến
Grading grid
P5 P6 P7 M4 M5 D2 D
❒ Summative Feedback: ❒ Resubmission Feedback:
Grade: Assessor Signature: Date:
Signature & Date:
- P5 Undertake a software investigation to meet a business need.
- A. Software Requirement Specification (The Tune Source)......................................................................
- JAD (team)
- Questionaire......................................................................................................................................
- Interview
- B. Identify the stakeholders, their roles, and interests in the case study
- Stakeholder and Development Team
- Stakeholder types and responsibilities
- C. Discuss the technique(s) you would use to obtain the requirements
- JAD...................................................................................................................................................
- Story Mapping
- Evaluation of the choice:.................................................................................................................
- D. Evaluate technical Requirement management
- supporting P6 Use appropriate software analysis tools/techniques to carry out a software investigation and create
- A. DFD (DATA FLOW DIAGRAM)..............................................................................................................
- Definition of Data Flow Diagram (DFD)...........................................................................................
- DFD Symbols
- DFD for the Tune Source project
- B. ERD
- C. Flowchart
- Search song on the web
- Purchase
- 3 Login and Register
- 4 Payment for the song (Buy song)
- 5 Gift a song to your friends
- P7 Explain how user and software requirements have been addressed in the design
- A. Requirements and functions for design
- B. Wireframe
- Register page (Tune Source Music).................................................................................................
- Login page (Tune Source Music)
- Home Page (Tune Source Music)
- Gift song to friend page
- Payment page
- REFERENCES
- Figure 1: Stakehoder Table of Figure
- Figure 2: Develop team
- Figure 3: Business Analyst
- Figure 4: Sponsor
- Figure 5: Story Mapping
- Figure 6: Example Data Flow Diagram (DFD)
- Figure 7: DFD Symbols
- Figure 8: Design DFD for Tune Source Online Music
- Figure 9: Design ERD Diagram Turn Source System....................................................................................
- Figure 10: Search Flowchart of the Tune Source Music
- Figure 11: Purchase items FlowChart
- Figure 12: Login and Register flowchart
- Figure 13: Payment for the song (Buy song)
- Figure 14: Gift a song to your friends (Flowchart)
- Figure 15: Wireframe for Register Page (Tune Source Music)....................................................................
- Figure 16: Wireframe for Login page (Tune Source Music)
- Figure 17: Wireframe for Home Page (Tune Source Music)
- Figure 18: Wireframe for Gift song to friend page (Tune Source Music)
- Figure 19: Wireframe for Payment page (Tune Source Music)
P5 Undertake a software investigation to
meet a business need.
A. Software Requirement Specification (The Tune Source)
Bellow are the three main methods I use to collect customer requests.
1. JAD (team)
Before starting the project, our team conducted a workshop to listen to the ideas of the team
members about the project.
The homepage should be designed in a style beautiful to attract customers, and on the homepage, there should be more options to choose songs. There must be a registration and login page for users to log in to use Web services. Login and registration information should be stored in the database. About page is a more detailed introduction to Web Tune Source. Websites should be processed with high speed The password of the user account must be encrypted to ensure the security of the user. There should be a detailed description of the song information when the user clicks on. Songs need to have high quality and sound to attract users. Should have the Cart Page so users can order the songs they like. The Web site must list out a list of friends that the user wants to give the song to.
2. Questionaire
We will list out a series of questions to list the customer's requirements in order to capture the
most essential things needed in the project.
We will list out a series of questions to list the customer's requirements in order to capture the most essential things needed in the project. Do you want to encrypt your password when you sign up for an account? Do you want to add music download function after you have purchased the product? Would you like to gift your friends the songs you bought? Do you want to look up a song title based on keywords you know related to that song? Would you like to use this WEB application on any electronic device you have? Do you like websites that process information at a fast pace?
3. Interview
In this section, I will proceed to ask the experts questions to gather more requirements. The questions asked are as follows: How to maintain a stable capital source without much influence from the external market ? (Financial expert answer)
Developer team A developer team is Software developers, sometimes referred to as product engineers, are members of a team that apply their knowledge of engineering and programming languages. Designers with experience have made the product easy to use and fun. They focus on end consumers while doing user interviews, market research, and product design.
Figure 2: Develop team
2. Stakeholder types and responsibilities
There are two types of stakeholders:
2.1 Internal stakeholders:
Organizations, entities, or groups with a stake in how the company operates are considered internal stakeholders. No matter what the organization's goals are, your life will be impacted by its success or failure. The second word for the internal stakeholder is Primary Stakeholders. The internal stakeholders of The Tune Source are: Business Analysts Business analysts (BAs) analyze processes, identify needs, and present data-driven recommendations and reports to executives and stakeholders to bridge the gap between IT and the business. In order to understand how data-driven enhancements to processes, goods, services, software, and hardware may increase efficiency and offer value, BAs collaborate with company executives and users. They must convey those ideas while also taking into account what is technically, financially, and operationally realistic. Depending on your function, you might use data sets to improve products, technology, equipment, software, services, or processes.
Figure 3: Business Analyst
Job description for a business analyst
BAs are responsible for creating new models to assist with business choices by closely cooperating with financial reporting and IT departments to establish initiatives and strategies to improve efficiency and save costs. You'll want "strong grasp of regulatory and reporting requirements as well as loads of skill in planning, budgeting, and financial analysis as well as a comprehension of important performance measures," according to Robert Half Technology. A typical job description for a business analyst includes: Constructing a comprehensive business analysis showcasing a company's problems, opportunities, and fixes Planning and budgeting Planning and observing Comparison of Variance Costing and reporting Identifying and expressing business requirements to stakeholders
Business analyst abilities Both hard and soft skills are necessary for the job of business analyst. Business analysts need to have the skills necessary to gather, assess, and report data trends as well as to share and use their expertise with others. All business analysts do not need to have an IT experience as long as they have a thorough understanding of how systems, products, and tools work. On the other hand, some business analysts are interested in making the switch from IT to this hybrid job even if they have a strong foundation in IT and limited business knowledge. The following are some of the most necessary abilities and experiences for a business analyst: Talents in communication and consultation Ability to facilitate Analytical thinking and problem-solving skills Being able to produce products that are of high quality and being detail-oriented Organization skills
The company Tune Source is based in southern California. Three industry veterans from the music industry—John Margolis, Megan Taylor, and Phil Cooper—founded Tune Source. The management of all operations falls to the network chief. They are in charge of all system activity, personnel decisions, and other system activities. The workstations' installation and upkeep fall under their purview. They insist that a secure login system be used to access all customer, employee, product, and service records.
Sponsor The sponsor for Tune Source Project is Carly Edwards.
Figure 4: Sponsor
User: Customers A customer is a person or company who makes a purchase from another company. Customers are essential to businesses because they generate revenue; without them, they would not exist. All businesses compete for customers by aggressively marketing their goods, lowering pricing to expand their clientele, or creating unique products and experiences that people enjoy. Think of TikTok, Google, Tesla, and Apple. Audiences As the whole public, this episode has entirely changed. The customer segment that the product is intended for is known as the target audience. Small groups are used in this episode, which is a spin-off from the original show with a huge audience. End-users An end-user is the individual for whom a software application or a hardware item is intended. The word derives from the notion that the "ultimate purpose" of a software or hardware product is to be helpful to the user. The end-user might be contrasted with the product's creators or programmers. End consumers are also separated from the product's installers or administrators.
C. Discuss the technique(s) you would use to obtain the
requirements
1. JAD
JAD (Joint Application Development) is a technique for including the client or end-user in the design and development of an application through a series of interactive workshops called JAD sessions. In the latter part of the 1970s, IBM's Chuck Morris and Tony Crawford developed JAD, which was initially introduced in workshops in 1980. Because the customer is involved at every stage of the development process, the JAD methodology is anticipated to provide speedier development timelines and higher levels of client satisfaction than more conventional methods. In the traditional approach to system development, the developer looks at the system requirements and develops an application while collecting user input through a series of interviews.
Phrases of the JAD Model
Learn about the JAD concept's stages and the model's design and development approach now that you are familiar with it: Define Specific Objectives: The facilitator sets all objectives and a list of items in partnership with stakeholders. These are then communicated to other developers and participants for comprehension and evaluation. This goal takes into account factors including the planned system's breadth, prospective results, required technology advancements, and more. Session Preparation: The facilitator is solely in charge of this preparation, which entails compiling all essential information and notifying other participants in advance. Research is carried out to better comprehend the system requirements and gather the necessary data for development. Session Conduct: The facilitator is in charge of determining the problems that need to be fixed for the system to operate without errors. While participating, the facilitator won't have any control over the information. 16 Documentation: Following the completion of the product, the records and papers that have been published are displayed at the meeting so that consumers and stakeholders may provide their approval.
Benefits of using JAD Model Improved Delivery Time: Compared to other earlier models, the JAD model is more effective and takes less time to manufacture a product. Cost savings: Less effort will be needed to build the system since needs and information were effectively assessed with company executives and stakeholders. The overall cost of development will be decreased as a consequence. Better Understanding: Product development is often better understood since the full demand is appraised by company leaders, followed by a thorough selection of engineers and team members who can professionally connect.
The second day is devoted to research and participation in order to build efficient communication. The third day is when everyone collaborates to find a solution and when output is at its highest. Building a team to accomplish the goals and validate the prototype. Step 5 : Choose participants For a workshop to be effective, these business users, IT experts, and outside specialists are needed. Create the workshop supplies. Step 6 : Plan ahead of time for the session. To help participants understand the project, this preparation should include visual aids like diagrams and documentation. Step 7: Plan the activities and exercises for the workshop. The workshop's facilitator should design exercises and activities to aid participants in learning, such as decomposition diagrams, high-level entity-relationship diagrams, or data model diagrams, among other types of diagrams. When the diagram to be used is selected, the facilitator designs tasks for the group to do during the workshop. The session will involve hands-on activities designed to help participants solve problems or work toward a specific goal. These activities will be carried out by smaller teams. To provide different perspectives on the project, these sub-teams could be made up of employees from various organizational departments. Step 8 : educate, enlighten and prepare the participants The attendees of the workshop should be aware of how it will be conducted, as well as its objectives and desired results. An internal organizational mailing might be used to accomplish this. Step 9: Plan the logistics of the workshop. All necessary equipment should be available in the workshop, including computers, a projector, paper, pencils, tables, and chairs.
2. Story Mapping
Definition of Story Mapping User stories may be arranged using the story mapping approach to get a more thorough picture of how they fit into the overall user experience. Depending on when a user would complete a certain task connected to their whole workflow with the product, the key stages of the customer journey (sometimes branded as epics, sometimes not) are arranged chronologically on a horizontal axis. The smaller steps that they roll up under are placed above the individual user stories. When a narrative map is complete, you can see all of the many ways a user may interact with a product from the first interaction to the fulfillment of the ultimate user goal in a coherent, logical viewpoint.
Figure 5: Story Mapping
What Are the Benefits of Story Mapping? Story mapping provides a variety of important functions. It gives a thorough image of how a product is utilized, which is often lost in the "not seeing the forest for the trees" reality of feature development because most teams concentrate on specific tasks rather than the "big picture" the majority of the time. Second, it may highlight functional flaws or places that need improvement since it may visually represent user experience gaps. Last but not least, a narrative map might be a helpful tool for prioritizing, both for an MVP (the absolute minimum needed to meet the overall objective) and later releases (what is lacking that must/should/could be there). When Should Story Mapping Be Used? The versatility of story mapping means that it may be applied at any stage of the life cycle of a product. Are you developing an MVP? An useful technique for figuring out the absolute minimal functionality needed to test your notion is a narrative map. It will prevent you from "forgetting" about crucial user experience elements that you may otherwise overlook. Trying to come up with improvements for version 1.0? By clearly illustrating all of the numerous enhancements you may do, a narrative map may assist your team in having excellent discussions about what will most impact your users. Is keeping up with your backlog a growing concern for you? By giving each item context and guiding prioritization and grouping with a big-picture view, story mapping aids with backlog control. Additionally, it may reveal gaps that you would not have seen otherwise. Consider adding a new product line. A narrative map will demonstrate what you now have and what is necessary to make the new feature operate in conjunction with your current offering. What Are Some Techniques for Using Story Mapping to Prioritize Roadmap Initiatives?
Story maps are a useful tool for adding to the process of route mapping. The highest priority features may be grouped into releases based on your team's capabilities and the release cycle once every potential item has been completely sketched out and prioritized. Sizing things up Arrange the smaller components in ascending order of relevance to complete your story map. After there, engage with product development to devote each item a proportionate
Process for managing requirements Have they been requested, recorded, and comprehended by all departments and stakeholders? Define the following requirement types: What requirements—functional and otherwise— exist? Put your necessary items in the following order: There could be additional paperwork for stakeholder evaluation. Set criteria in order of importance: Not all specifications are created equal. If a requirement has been satisfied, if it has many dependents, it moves up the list to ensure that it won't hold back a lot of other items. Additional obligations But what if it's a one-time demand? After then, it might be given lower priority. Make a trail: One of the most crucial elements of effective requirements management is traceability. Stakeholders and team members may learn why a requirement is necessary, what changes have been made, and whether it is complete by tracing your requirements. Use a versioning or numbering system: This makes sure that the most current milestone is continually being worked on and enables stakeholders and team members to see how many changes have been made at each milestone. Develop a communication plan: It is better to be as honest as possible when documenting everything, as was previously said.
From the Requirements Collection Methods and the discussion of the above methods, I have drawn the final inference about the requirements of the project as follows:
Requirement ID Requirement Description
Stakeholde r Functional Requirement
Non- functional Requirement and technical
Feasibility Organization
RQ.1 All user data information must be stored in the database.
Dev team Store infomation Information is stored in Database
Yes Allowed
RQ.2 The system must encode the password to the database
Dev Team High-Security Hashing, Encoding
Yes Allowed
RQ.3 Users view all songs and view detail descriptions of the songs
Marketing Display all songs Render elements of top trend songs from database to homepage
Yes Allowed
RQ.4 When users click on the song, user can buy the song
Marketing Buying song Insert information about the user and song into the Order table.
Yes Allowed
RQ.5 After user has bought the song, they can also gift the song to their chosen friend.
Customers Gift song Send a direct to the user id who was chosen by the customer have given the gift(song).
Yes Allowed
P6 Use appropriate software analysis
tools/techniques to carry out a software
investigation and create supporting
A. DFD (DATA FLOW DIAGRAM)
1. Definition of Data Flow Diagram (DFD)
A data flow diagram (DFD) shows how information moves through any system or process.
Using preset symbols like rectangles, circles, and arrows as well as short text labels, it displays
data inputs, outputs, storage locations, and the routes between each destination. Data flow
diagrams can range from straightforward, even hand-drawn, process summaries to intricate, multi-level DFDs that go in-depth into many aspects of data processing. They can be utilized to
analyze or imitate an existing system. For both technical and non-technical audiences, from
developers to CEOs, a DFD, like all the best diagrams and charts, typically "expresses" things
graphically that are challenging to explain in words.
Figure 6: Example Data Flow Diagram (DFD)
2. DFD Symbols
Figure 7: DFD Symbols
Notation for DFD:
An external entity is a system that sends or receives data from the system being diagrammed in order to communicate with it. They serve as the starting and ending points for data entering and leaving the system. They could be a computer system, a person or group from outside the company, or a business system. They are also known by the
