Đang tải... (xem toàn văn)
Điểm của bài asm còn tùy thuộc vào người chấm. Chỉ cần paraphase bài này là có thể pass. 1 trong nhưng tool paraphase mình recommend là quillbot.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.3 andmargins to be as follows: left = 1.25cm, right = 1cm, top = 1cm, bottom = 1cm. Citation andreferences must follow the Harvard referencing style. ASSIGNMENT FRONT SHEET Qualification BTEC Level HND Diploma in Computing Unit number and title Unit 2: Networking Infrastructure Submission date Date Received 1st submission Resubmission Date Date Received 2nd submission Student Name Student ID Class 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 Grading grid P1 P2 P3 P4 M1 M2 D1 ❒ Summative Feedback: Grade: Lecturer Signature: ❒ Resubmission Feedback: Assessor Signature: Date: Table of Contents I Network Network definiton Ξ First of all, network also known as computer networking, which can be understand as a group of computers utilizing a principles of general communication protocols over digital connections for the intention of sharing resources located upon or accommodated by network nodes The operation of network transporting and exchanging data between nodes over a shared medium in an information system, depend on material wireless, optical and wired radio frequency methods which may be regulated in a variety of network frames (Anon., n.d.) Figure : Illustrated image of network Ξ Advantages of networking: File sharing – youll easily share data between different users, or access it remotely if you keep it on other connected devices Resource sharing – using networkconnected peripheral
ASSIGNMENT 01 FRONT SHEET Qualification BTEC Level 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 Student ID Class Assessor name Michael Omar Student declaration I certify that the assignment submission is entirely my 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 P1 P2 P3 P4 M1 M2 D1 D2 1|Page ❒ Summative Feedback: Grade: ❒ Resubmission Feedback: Assessor Signature: Date: Internal Verifier’s Comments: Signature & Date: 2|Page Table of Contents TABLE OF CONTENTS TABLE OF FIGURES LIST OF TABLES A INTRODUCTION B SDLC MODEL I DESCRIBE TWO ITERATIVE AND TWO SEQUENTIAL SOFTWARE LIFECYCLE MODELS (P1) SDLC Models a) Prototyping model b) Waterfall model c) Spiral Model .10 d) Scrum Model 12 e) V-Model 14 SDLC Model is Suitable for TuneSource Project and Explain 16 Discuss The Suitability Of Each Of The SDLC Models For The Project .17 I EXPLAIN HOW RISK IS MANAGED IN THE SPIRAL LIFECYCLE MODEL (P2) 19 Risk Management Process 19 a) Definition: The process of identifying, monitoring, analysing and managing possible risks to reduce the negative impact they may have on a company is known as the risk management process Security breaches, data loss, cyberattacks, system failures, and natural disasters are all examples of potential dangers A good risk management process will aid in determining which hazards pose the greatest threat to a company and provide instructions for dealing with them (Reciprocity, 2020 ) 19 b) essential steps of the Risk Management Process 19 c) The Importance of Risk Management Process: 20 d) Risk Management In The Spiral Lifecycle Model 20 e) Risk Management Matrix 21 C FEASIBILITY STUDY .22 I DISCUSS THE PURPOSE OF CONDUCTING A FEASIBILITY STUDY FOR THE PROJECT 22 What is Feasibility Study .22 The Importance of Feasibility Study 22 The Purpose of Conducting a Feasibility Study for Tune Source Project 22 1|Page The Benefits of Conducting a Feasibility Study: 23 II EXPLAIN THE PURPOSE OF A FEASIBILITY REPORT (P3) 23 1) Three Feasibility Criteria .23 a Technical Feasibility .23 b Economic Feasibility 23 c Organizational Feasibility .24 2) How The Three Feasibilities Are Applied To The Tune Source Project 24 3) Discuss alternative technical solutions using the alternative matrix 32 4) Explain the components of a feasibility report 33 5) Describe How Technical Solutions Can Be Compared (P4) 36 REFERENCES 38 Table of Figures Figure 1: SDLC .4 Figure 2: Prototyping model Figure 3: Waterfall model .7 Figure 4: Spiral model 10 Figure 5: Scrum methodology 12 Figure 6: V-model .14 Figure 7: Risk management process 19 Figure 8: Feasibility Study 22 Figure 9: Payback analysis candidate 27 Figure 10:Payback analysis .31 List of Tables Table 1: The Suitability Of SDLC models 17 Table 2: Risk Management Matrix .21 Table 3: Cost for TuneSource project Candidate .25 Table 4: Cost for project (candidate 2) .28 Table 5: Comparison matrix of two candidates 33 2|Page Table 6: Diagram of alternative matrix .37 3|Page A INTRODUCTION The Software Development Life Cycle (SDLC) can be viewed as a well-defined procedure for producing high-quality, low-cost software in the shortest amount of time possible The SDLC's purpose is to create exceptional software that exceeds all customer expectations and demands The SDLC is a step-by-step process that specifies and explains a detailed plan with stages, or phases, that each has its methodology and deliverables Figure 1: SDLC This report will deeply present and show two crucial components in the SDLC process that is SDLC models and Feasibility Study based on studying and working in the TuneSource Project 4|Page B SDLC MODEL I Describe Two Iterative And Two Sequential Software Lifecycle Models (P1) SDLC Models a) Prototyping model Figure 2: Prototyping model One of the most Definition: commonly utilised Software Development Life Cycle Models is the Prototyping Model This paradigm is applied when customers not know the exact project requirements ahead of time In this model, an end-product prototype is first created, then tested and refined based on user feedback until a final acceptable prototype is established, which serves as the foundation for building the final product (Pedamkar, 2020) Phases of the Prototyping Model Communication: This is the phase in which the developer and client schedule a meeting to discuss the software's goals and objectives Design: The design phase was completed fast because all needs were met on both the providing and receiving sides It's what's used to make the prototype It covers the essential features of the software, such as input and output, but is primarily concerned with visible elements rather than planned actions Modelling: It gives you a better notion of what the software needs and gives you a better grasp of the software 5|Page Deployment: The client examines the program before deployment, and if the client is not pleased, the product is refined to meet the client's needs This process continues until the client's needs are not met The product is finally deployed to the production environment after the client is satisfied with it It is thoroughly analyzed and tested, and regular maintenance is performed (Pedamkar, 2020) When to use Prototype-Model: It should be utilized when the end-user must interact with a lot of final systems, such as online systems, web applications, or interfaces These receive the most traffic from visitors who check and utilize them regularly The system's development does necessitate the use of trained personnel It also necessitates constant client availability for input, evaluation, and sign-off on the various prototypes created Advantages and Disadvantages of Prototype Model ☺ ☺ ☺ ☺ ☺ ☺ Advantages Customers get to see a portion of the finished product early in the life cycle Customers will be more satisfied and comfortable as a result of this Because there is room for improvement, new requirements can be easily met Functionalities that aren't present can simply be discovered Errors may be spotted considerably sooner, saving time and money while also improving the quality of the product The produced prototype can be reused by the developer in the future for more complex applications Design flexibility Disadvantages The user may find it difficult to distinguish between the genuine product or system and the prototype When there are insufficient needs, the prototype model does not work It adds to the system's complexity as well as its deadlines It is not possible to develop the new system using the existing prototype Building a system prototype might take a lot of time and work The prototype development process is sometimes known as a sluggish process because it takes a long time When there are a lot of changes, the client may become confused and lose interest It also reduces the development team's productivity Why Prototype model is selected for a development environment 6|Page It provides a clear picture of the software in development to the client before and during the implementation stage It aids in the prevention of complications that may arise in the future It facilitates client-developer communication so that the product meets the client's needs and is easier to grasp for developers from the customer's perspective The prototype model also includes a variety of models b) Waterfall model Definition: The waterfall model is one of the first models of software development in which activities are completed in sequential order, beginning with feasibility and progressing through various tasks until live implementation Requirements feed into the design, which feeds into the construction or implementation, and eventually into the testing It's been difficult to get feeds passed back up the waterfall because the testing process occurs at the end of the model (Pedamkar, 2020) Figure 3: Waterfall model Phases of the Waterfall Model Requirement: Specify what functionality is needed to develop and design and what processes to develop It supplies raw materials for the product being manufactured, allowing the impending product to be researched, finalized, and labelled It also allows us to decide on the product's hardware or software needs, which will be planned, developed, and captured along the process 7|Page Analysis: It results in designing models, schema, and business rules: o Information and requirement for the product development are gathered from the customer and then it is processed for analysis to eradicate incompleteness and inconsistencies related to software product development o An SRS (software requirement specification) document is used to document the above-mentioned requirements It acts as a link between the customer and the development team at SRS Design: The next most significant phase to study is system design In this phase, the requirement specification is largely researched and verified It also aids in the transformation of the SRS document into the software product's functional design and development Converting the requirements acquired in the SRS into a format that can be coded in a programming language As a result, it can be said that one creates the overall architecture for the software development project during the designing phase Implementation: Inputs from the system design are taken in this phase, and they are first turned into little programs known as units Each unit in the implementation phase is developed and tested to ensure full functionality, a process known as unit testing This step translates the system design into source code with fully functional program modules It entails the software's development, testing, and integration Integration and Testing: Testing each unit from the implementation phase which is then integrated into a module or system for various tests such as load tests, load tests, and so on The testing environment is subjected to a continuous software check to see whether any flows or errors in the design or code exist Deployment: The software product is deployed to the user or customer system or launched to the market after non-functional, functional, alpha, and beta testing is completed Maintenance: Maintenance can be divided into three types, as shown below: 8|Page ... .10 d) Scrum Model 12 e) V-Model 14 SDLC Model is Suitable for TuneSource Project and Explain 16 Discuss The Suitability Of Each Of The SDLC. .. 27 Figure 10 :Payback analysis . 31 List of Tables Table 1: The Suitability Of SDLC models 17 Table 2: Risk Management Matrix . 21 Table 3:... the cost and time to develop the software 16 | P a g e Discuss The Suitability Of Each Of The SDLC Models For The Project Table 1: The Suitability Of SDLC models Alternative models Waterfall Suitable