Ask a question from expert

Ask now

Unit 9: Software Development Life Cycle

46 Pages9041 Words1314 Views
   

Added on  2020-10-26

Unit 9: Software Development Life Cycle

   Added on 2020-10-26

BookmarkShareRelated Documents
1 ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 9: Software Development Life CycleSubmission date 11/10/2020 Date Received 1st submissionRe-submission DateDate Received 2nd submissionStudent Name DUONG VAN DAT Student ID BHAF190049 Class BH-AF-1911-2.1 Assessor name NGO THI MAI LOAN 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 D4
Unit 9: Software Development Life Cycle_1
2 Summative Feedback: Resubmission Feedback:Grade:Assessor Signature:Date:Signature & Date:
Unit 9: Software Development Life Cycle_2
3 Table of Content A.Under taken a software investigation to meet the business need .......................................... 6I.Requirement collection techniques ...................................................................................... 61.Interview ........................................................................................................................... 72.Some other requirement collection techniques: ............................................................ 12II.Requirement analysis techniques ....................................................................................... 171.BPA – Business Process Automation ............................................................................... 182.BPI – Business Process Improvement ............................................................................. 183.BPR – Business Process Reengineering ........................................................................... 194.Choose suitable technique for Tune Source. .................................................................. 20B.Use appropriate software analysis tools/techniques to carry out a software investigation and create supporting documentation. .................................................................................. 221.Activity diagram .................................................................................................................. 222.Use case diagram ................................................................................................................ 233.Data flow diagram ............................................................................................................... 25a.Context level ................................................................................................................... 26b.Level 1 DFD...................................................................................................................... 264.Entity relationship diagram (ERD) ....................................................................................... 27C.Explain how user and software requirements have been addressed. ................................... 31I.Relational Database ............................................................................................................ 31II.Wireframe ........................................................................................................................... 341.Wireframe introduction .................................................................................................. 342.Wireframe of the website ............................................................................................... 35III.The functionality of the site ................................................................................................ 401.Login ................................................................................................................................ 402.Register ........................................................................................................................... 413.Functions to display, add, edit, and delete songs and users .......................................... 43
Unit 9: Software Development Life Cycle_3
4 List of figures Figure 1. Interview report 1 .......................................................................................................... 10Figure 2. Interview report 2 .......................................................................................................... 11Figure 3. Interview report 3 .......................................................................................................... 12Figure 4. JAD meeting ................................................................................................................... 13Figure 5. BPA ................................................................................................................................. 18Figure 6. BPI .................................................................................................................................. 19Figure 7. BPR ................................................................................................................................. 20Figure 8. Activity diagram for admin ............................................................................................ 22Figure 9. Activity diagram for users .............................................................................................. 23Figure 10. Use case diagram for users .......................................................................................... 24Figure 11. Use case diagram for admin ........................................................................................ 25Figure 12. Context level ................................................................................................................ 26Figure 13. Level 1 DFD................................................................................................................... 27Figure 14. Entity relationship diagram .......................................................................................... 30Figure 15. create song table ......................................................................................................... 31Figure 16. create users table......................................................................................................... 32Figure 17. create orders table ....................................................................................................... 32Figure 18. create table order_deail .............................................................................................. 33Figure 19. create table genre ........................................................................................................ 33Figure 20. create table artists ....................................................................................................... 33Figure 21. Relational database ..................................................................................................... 34Figure 22. Home Page Wireframe ................................................................................................ 36Figure 23. Login Wireframe .......................................................................................................... 37Figure 24. Register wireframe ...................................................................................................... 38Figure 25. Admin area wireframe ................................................................................................. 39Figure 26. Management page wireframe ..................................................................................... 40Figure 27. Login function .............................................................................................................. 41Figure 28. Register function .......................................................................................................... 42Figure 29. Song management function ......................................................................................... 43Figure 30. Add function................................................................................................................. 44Figure 31. Delete function ............................................................................................................ 44
Unit 9: Software Development Life Cycle_4
5 List of tables Table 1. Choose interviewee ........................................................................................................... 7Table 2. Choose questions .............................................................................................................. 8Table 3. Advantage and disadvantage of JAD ............................................................................... 14Table 4. Advantages and disadvantages of questionnaire ........................................................... 15Table 5. Advantages and disadvantages of document analysis ................................................... 16Table 6. Advantages and disadvantages of observation .............................................................. 17Table 7. Technical evaluation. ...................................................................................................... 21Table 8. Entities and attributes ..................................................................................................... 28
Unit 9: Software Development Life Cycle_5
6 Introduction In this report, I will provide knowledge of request collection techniques, including 5 techniques: interview, questionnaire, JAD, document analysis, observation. In it, I have given the definitions and the factors associated with them. I have also provided the application of the interview technique to pave the way for Tune Source project development. Furthermore, I also studied requirements analysis techniques such as BPI, BPA, BPR and selected the most suitable one for this project. Furthermore, I created diagrams for Tune Source's system design such as: use case diagram, activity diagram, data flow diagram, and entity relationship diagram. From the entity relationship diagram, I have created a relational database with all the information and data needed by Tune Source's system. In addition, I also create a report on the functions of the website, which includes the wireframe and the main functions of the system. A.Under taken a software investigation to meet the business need The second stage of the system development life cycle is the analysis phase. The analysis phase is the most important stage in SDLC. For example, when a new or upgraded system is introduced into an organization, it is often intended to support the work the organization has already performed. Although the new system may differ substantially from the existing system, the information being processed and the main functions of the system will remain unchanged. Hence, analysis of existing systems provides a solid basis for new system design. This phase can be divided into two processes: requirements collection and requirements analysis. To implement them fully, they use suitable techniques such as requirement collection technique, requirement analysis technique. I.Requirement collection techniques In any software development process, requirements collection is essential. Requirement collection is a very important job in ensuring the success of the project, which is the basis for defining the project management objectives, methodology and content. requirements, we can understand their needs and problems, thereby giving the best solution. There are
Unit 9: Software Development Life Cycle_6
7 many techniques for requirement collection but the technique we chose for the Tune Source project is the interviewing technique. 1.Interview Interviewing is the most common technique for requirement collection, as well as one of the main sources of inquiry. To help get the most out of an interview, they should think and prepare well before sitting with the interviewee. Analysts should identify stakeholders to be interviewed. These could be the users who interact with the existing or new system, the management board, the project sponsor or anyone else involved with the system. When preparing an interview, it is important to ask open-ended questions, as well as open-ended questions. Open-ended questions often help to gain valuable information, based on many different individuals and how they interact or view different systems. Steps to conduct interviews: Step 1: Choose people to be interviewed We need to identify the stakeholders to be interviewed. These can be users who interact with the existing or new system, the management board, the project sponsor or anyone else related to the system such as the client and could be any artist or singer. Since then, we have selected a few people to interview as follows: Table 1. Choose interviewee Full Name Role Interview purposes Date time John Margolis Chief Execute Officer Direction and strategic vision for the system 10/09/2020 Megan Taylor Chief Technology Officer Technology requirements for the new system, as well as existing Tune Source technologies. 11/09/2020 Phil Cooper Sales Manager Tune Source's business level and customer outreach reviews 12/09/2020 Johnny Do Customer Customer requirements to the system 12/09/2020
Unit 9: Software Development Life Cycle_7
8 Step 2: Design interview question We will ask some open and closed questions to open up the problem, to know the actual situation of the company, to clearly request functionality and expectations from the business. Here are some example questions: Table 2. Choose questions Types of question Questions Closed-ended question Are Tune Source customers comfortable to use the new system? Would you please answer some questions? Does Tune Source have old customer data? What additional information do you want the new system to provide? How many records are sold per day? What do you think about the current system? How do customers make an order? Open-ended question What is the company's desire for this new system? What are the system requirements to attract potential customers? What are the strengths and weaknesses of Tune Source? What is the direction of Tune Source for the new system in the next 5 years? Who are the target customers of the system? How do you decide what types of marketing campaign to run? What are some problems? Probing questions Can you explain that in a bit more detail? Why? Can you give me some example?
Unit 9: Software Development Life Cycle_8

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
The assignment submission is entirely my own work and I understand the consequences of plagiarism
|75
|6901
|487

Database Design & Development Assignment 2
|75
|6962
|200

Database in Software Engineer
|27
|3556
|21

Order and Components - Thesis and Dissertation Guide
|8
|967
|75

Unit 1: Programming Submission PDF
|36
|7565
|62

Unit 43: Internet of Things PDF
|43
|9819
|457