Second Semester Bikash Bista Department of IT, ISMT College SDLC Prof. Kamal Dhakal 1th Jan, 2022 SDLC INTERNATIONAL SCHOOL OF MANAGEMENT & TECHN ASSIGNMENT COVER SHEET STUDENT DETAILS Student ID Bikash Bista Reg No. Family Name Given Name Bikash Bista Enrolment Year 2019 Section j Email bikashb@ismt.edu.np Semester 2nd sem UNIT DETAILS Unit Title Sofware Lifecycle Devlopment Unit Code Assessor Name Kamal Dhakal Assignment Title College Management System Development Lifecycle Assignment No 1/1 Qualification BTEC HND COMPUTING Issued Date J/615/1361-Unit 9 5/31/2021 Submission Date IN Campus 07/31/2021 ISMT college Bikash Bista 2ndsem (HND) 1 SDLC STUDENT ASSESSMENT SUBMISSION AND DECLARATION When submitting evidence for assessment, each student must sign a declaration confirming that the work is their own. Student Name Bikash Bista Assessor Name Kamal Dhakal Issue Date 05/31/2021 Submission Date 07/31/2021 Programme BTEC HND IN COMPUTING Unit Name Software Development Lifecycle Assignment Title College Management System Development Lifecycle Plagiarism Plagiarism is a particular form of cheating. Plagiarism must be avoided at all costs and students who break the rules, however innocently, may be penalized. It is your responsibility to ensure that you understand correct referencing practices. As a university level student, you are expected to use appropriate references throughout and keep carefully detailed notes of all your sources of materials for material you have used in your work, including any material downloaded from the Internet. Please consult the relevant unit lecturer or your course tutor if you need any further advice. 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 signature: Date: 01/01/2022 Pearson Education 2018 Higher Education Qualifications Bikash Bista 2ndsem (HND) 2 SDLC INTERNATIONAL SCHOOL OF MANAGEMENT AND TECHNOLOGY KATHMANDU, NEPAL Qualification BTEC HND IN COMPUTING Student Name Unit Number & Title J/615/1631 – Unit 9: Software Development Lifecycle Assessor Name Kamal Dhakal Completion Date Assignment Launch Date Due Date 05/31/2021 07/31/2021 Session/Year 01/2019 Assignment Number 1/1 Assignment Title College Management System Development Lifecycle Assignment submission format Each student has to submit their assignment as guided in the assignment brief. The students are guided what sort of information is to produce to meet the criteria targeted. You are required to make use of headings, paragraphs and subsections as appropriate, and all work must be supported with research and referenced using the APA referencing system. Learning outcomes covered LO1 Describe different software development lifecycles. LO2 Explain the importance of a feasibility study. LO3 Undertake a software development lifecycle. LO4 Discuss the suitability of software behavioural design techniques. Bikash Bista 2ndsem (HND) 3 SDLC Scenario 1 New Republica College which is predominantly operating in Nepal is offering an education to many nationals and international students. You work as a systems analyst for a New Republica college which is developing the new college management system. This system will handle college accounting system, library management and assignment tracking system. The college has a small systems development team which in the past has been solely responsible for all development work. The Principal of the College feels that the development team has not been outward looking and wants a fresh approach for the new system. The in-house team will work alongside analysts and developers from your team who will lead the project. You will be project managing the analysis and design stage of the new system. Your first task is to update the in-house team on the developments in new methodologies used to analyze systems. Most of the in-house team uses only the more traditional approaches and few are fully aware of the agile methodologies which are growing in popularity. Assignment Task – Part 1 As a part of your responsibility, you are required to prepare a report that describes different software development cycles. Your report must include the following: 1. Description of predictive and adaptive software development models considering at least two iterative and two sequential models. 2. The risks involved in each of the models and how the risk can be mitigated /managed in each model by taking a reference of the spiral model. Once you have prepared the report you are required to produce documentation that 3. Describe with an example why a particular lifecycle model is selected for a development environment. You may consider a different development environment with different business logics, platform, etc., and the applicability of the particular software development model over the development environment. 4. Assess the merits of applying the waterfall model to a large software development project with appropriate evidenced researched work with reference to the current context. Bikash Bista 2ndsem (HND) 4 SDLC Assignment Task – Part 2 1. You are required to produce a documentation that explains the purpose of the feasibility report and describe how technical solutions can be compared. 2. Prepare a brief report discussing the components of the feasibility report. 3. Carry out the feasibility study as per the best of your previous research work against the solution to be developed for the given problem and assess the impact of different feasibility criteria on the software investigation. Assignment Task – Part 3 1. Undertake the software investigation to meet the business need using appropriate software analysis tools/techniques to carry out a software investigation and create a supporting documentation. You may submit this task in the form a report structured with background information, problem statements, data collection process and summary etc. In order to carry out the systems investigation you are required to identify the stakeholders, identify the requirements of the client, specify the scopes like inputs, outputs, processes and the process descriptors, consideration of alternative solutions and security considerations and the quality assurance applied. You are also required to identity the constraints like costs, organizational policies, legacy systems, hardware requirements etc. For software analysis you may use the following tools: Data Flow Diagram up to second level Entity Relationship Diagram 2. Reference to your task above that required some level of intensive research work analyse how software requirements can be traced throughout the software lifecycle. 3. Discuss different approaches to improve the software quality and considering the above context discusses the two approaches that can be applied at this context to improve the software quality. 4. Critically evaluate how the use of the function design paradigm in the software Bikash Bista 2ndsem (HND) 5 SDLC development lifecycle can improve the software quality. Support your ideas with reference to the tasks you have done. Assignment Task – Part 4 1. Prepare a documentation that explains how user and software requirements have been addressed. You may tabulate this task with the columns that has the expected client requirements and the actual output of the product to be developed after the appropriate analysis. 2. Discuss about the different software specification methods and suggest two software behavioral specification methods and illustrate their use with an example relevant to the project that needs to be constructed for the given context. Some of the software specification techniques include flowcharts, pseudo code and formal specification methods and so on. 3. Differentiate between finite state machines (FSM) and an extended Finite State providing an application for both. 4. Present justifications of how data driven software can improve the reliability and effectiveness of the software. Pass Merit LO1 Describe different software development lifecycles P1 Describe two iterative and M1 Discuss, with an example, two sequential software why a particular lifecycle model lifecycle models. is selected for a development environment. P2 Explain how risk is managed in these models. LO2 Explain the importance of a feasibility study P3 Explain the purpose of a M2 Discuss the components of a feasibility report. feasibility report Distinction D1 Assess the merits of applying the Waterfall lifecycle model to a large software development project. D2 Assess the impact of different feasibility criteria on a software investigation. P4 Describe how technical solutions can be compared. LO3 Undertake a software development lifecycle P5 Undertake a software M3 Analyse how software D3 Evaluate the process investigation to meet a requirements can be traced of undertaking a systems Bikash Bista 2ndsem (HND) 6 SDLC business need. throughout lifecycle. the software investigation with regards to its effectiveness in P6 Use appropriate software improving software analysis tools/techniques to M4 Discuss two approaches to quality. carry out a software improving software quality. investigation and create supporting documentation LO4 Discuss the suitability of software behavioural design techniques P7 Discuss using examples the M5 Analyse a range of software D4 Present justifications suitability of software behavioural tools and of how data driven behavioural design techniques. software can improve the techniques. reliability and M6 Differentiate between a effectiveness of software. finite state machine (FSM) and an extended-FSM, providing an application for both. Grades Achieved Note: Refer the unit details provided in your handbook when responding all the tasks above. Make sure that you have understood and developed your response that matches the highlighted key words in each task. Plagiarism Notice You are remined that there exist Academic Misconduct Policy and Regulation concerning Cheating and Plagiarism. Extracts from the Policy: Section 3.4.1: Allowing others to do assignments / copying others assignment is an offence Section 3.4.2: Plagiarism, using the views, opinion or insights / paraphrasing of another person’s original phraseology without acknowledgement Requirements It should be the student’s own work – Plagiarism is unacceptable. Clarity of expression and structure are important features. Bikash Bista 2ndsem (HND) 7 SDLC Your work should be submitted as a well presented, word-processed document with headers and footers, and headings and subheadings, both in hard and soft copies. You are expected to undertake research on this subject using books from the Library, and resources available on the Internet. Any sources of information should be listed as references at the end of your document and these sources should be referenced within the text of your document using APA Referencing style Your report should be illustrated with screen-prints, images, tables, charts and/or graphics. All assignments must be typed in Times New Roman, font size 12, 11/2 spacing. The center policy is that you must submit your work within due date to achieve “Merit” and “Distinction”. Late submission automatically eliminates your chance of achieving “Merit and Distinction”. Also, 80% attendance is required to validate this assignment. I declare that all the work submitted for this assignment is my own work and I understand that if any part of the work submitted for this assignment is found to be plagiarised, none of the work submitted will be allowed to count towards the assessment of the assignment. Assignment Prepared By Signature Kamal Dhakal Brief Checked By Dhruba Babu Joshi Date Feb 08, 2021 Signature Date Feb 12, 2021 Table of Contents [P1].......................................................................................................................................................12 Describe two sequential and two iterative life cycle models...............................................................12 Introduction:.........................................................................................................................................12 System Development Life Cycle (SDLC)............................................................................................12 1. Waterfall model............................................................................................................................12 Advantages of Waterfall model............................................................................................................14 Disadvantages of waterfall model:.......................................................................................................15 2. V-Model............................................................................................................................................15 Advantages of V model........................................................................................................................17 Bikash Bista 2ndsem (HND) 8 SDLC Disadvantages of V-Model...................................................................................................................17 Agile model:.........................................................................................................................................17 Advantages of Agile Lifecycle model..................................................................................................19 Disadvantages of Agile Lifecycle model.............................................................................................19 Spiral Model:........................................................................................................................................20 Part 2:...................................................................................................................................................22 You are required to produce a document that explain the purpose of the feasibility report and describe how technical solutions can be compared............................................................................................22 Purpose of feasibility study..................................................................................................................22 Comparison of Technical Solution:......................................................................................................23 Conclusion:..........................................................................................................................................24 P3:........................................................................................................................................................25 Undertake a software development lifecycle.......................................................................................25 Introduction:.........................................................................................................................................26 Required features in the new software.................................................................................................27 Planning of the software.......................................................................................................................28 Selection of the software development lifecycle model......................................................................28 Using appropriate software analysis tool.............................................................................................28 Design of the software.........................................................................................................................29 Data flow diagram of the software.......................................................................................................29 Entity relationship diagram..................................................................................................................30 Conclusion............................................................................................................................................30 PART IV:..............................................................................................................................................31 SUITABILITY OF SOFTWARE BEHAVIOURAL DESIGN TECHNIQUES..................................31 Suitability of the software....................................................................................................................31 Conclusion:..........................................................................................................................................32 References............................................................................................................................................33 Bikash Bista 2ndsem (HND) 9 SDLC [P1] Describe two sequential and two iterative life cycle models. Introduction: In order to develop or build the information system we have to organize the task in order to build the applications successfully and in a systematic way and for organizing the working way we need to follow the SDLC lifecycle. Thus, this task, will cover the basic definition of SDLC and then we will describe two sequential as well as iterative models of System Development Lifecycle. System Development Life Cycle (SDLC) SDLC Stands for "System Development Lifecycle." SDLC is a structured approach to creating and maintaining a system used in information technology. It can be applied to networks and online services, but is most often used in software development. Bikash Bista 2ndsem (HND) 10 SDLC When applied to software, the SDLC is also called the "application development life-cycle." Some SDLC models have as few as five stages, while others have as many as ten. A typical SDLC framework used for developing a software application might include the following seven stages: Planning, defining, designing, building testing deployment, maintenance. I am going to describe about predictive and adaptive software development models considering at least two iterative and two sequential models. 1. Waterfall model: The Waterfall Model was the first Process Model to be introduced. It is also referred to as a linearsequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases. It is the earliest SDLC approach that was used for software development. It illustrates the software development process in a linear sequential flow. This means that any phase in the development process begins only if the previous phase is complete. In this waterfall model, the phases do not overlap.. Waterfall process has six phases such as requirement gathering and analysis, system design, implementation, testing, deployment of system, maintenance. The following figure is a graphical representation of the various stages of a typical SDLC. Bikash Bista 2ndsem (HND) 11 SDLC . Phases of development in the waterfall model are thus discrete, and there is no jumping back and forth or overlap between them. As seen in the above figure, first the designer should gather required data and information and he have to analyses the data.So the description of the stages of waterfall model as following: a. Planning - The most fundamental part of the SDLC is planning. This includes steps like determining a need for a specific program, who will be the end users, what the development will cost, and how long it will take. b. Defining - In this stage, the general development plan is funneled into specific criteria. The specific requirements of the program are defined. At this stage, the development team may also decide what programming language should be used to build the program. c. Designing - This process involves creating the user interface and determining how the program will function. For larger applications, it is common to create a design document specification (DDS), which may need to be reviewed and approved before the actual development begins. Bikash Bista 2ndsem (HND) 12 SDLC d. Building - The building stage typically comprises the bulk of the software development process. It includes programming the source code, creating the graphics, and compiling the assets into an executable program. Small projects may involve a single programmer, while larger projects may include multiple teams working together. For example, one team might design the user interface, while another team writes the source code. For multiplatform applications, individual teams may be assigned to different platforms. e. Testing - The all-important testing phase allows the developer to catch unknown issues and fix any bugs that arise in the program. Some testing may be done internally, while a beta version of the software might be provided to a select group of users for public testing. f. Deployment - Once a program has passed the testing phase, it is ready for deployment. In this stage, the software is released to the public. It may be provided via an electronic download or as boxed software, which comes on a CD or DVD. g. Maintenance - After a software application has been released, there may still be additional bugs or feature requests submitted by users. The development team must maintain the software by fixing bugs and adding new features. Commercial software programs often include some level of technical support. Advantages of Waterfall model Simple and easy to understand and use Easy to manage due to the rigidity of the model. Each phase has specific deliverables and a review process. Phases are processed and completed one at a time. Works well for smaller projects where requirements are very well understood. Clearly defined stages. Well understood milestones. Bikash Bista 2ndsem (HND) 13 SDLC Easy to arrange tasks. Process and results are well documented. Disadvantages of waterfall model: No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for the projects where requirements are at a moderate to high risk of changing. So, risk and uncertainty is high with this process model. It is difficult to measure progress within stages. Cannot accommodate changing requirements. Adjusting scope during the life cycle can end a project. Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or business bottleneck or challenges early. 2. V-Model The V-model is a type of SDLC model where process executes in a sequential manner in V-shape. It is also known as Verification and Validation model. It is based on the association of a testing phase for each corresponding development stage. Development of each step directly associated with the testing phase. The next phase starts only after completion of the previous phase i.e. for each development activity, there is a testing activity corresponding to it. Bikash Bista 2ndsem (HND) 14 SDLC All the process of V-model are described follows: 1. Verification phase: It involves static analysis technique (review) done without executing code. It is the process of evaluation of the product development phase to find whether specified requirements meet. 2. Coding phase: The actual coding of the system modules designed in the design phase is taken up in the Coding phase. The best suitable programming language is decided based on the system and architectural requirements.The coding is performed based on the coding guidelines and standards. The code goes through numerous code reviews and is optimized for best performance before the final build is checked into the repository. 3. Validation phase: It involves dynamic analysis technique (functional, non-functional), testing done by executing code. Validation is the process to evaluate the software after the completion of the development phase to determine whether software meets the customer expectations and requirements. Bikash Bista 2ndsem (HND) 15 SDLC Advantages of V model: This is a highly disciplined model and Phases are completed one at a time. V-Model is used for small projects where project requirements are clear. Simple and easy to understand and use. This model focuses on verification and validation activities early in the life cycle thereby enhancing the probability of building an error-free and good quality product. It enables project management to track progress accurately. Disadvantages of V-Model: High risk and uncertainty. It is not a good for complex and object-oriented projects. It is not suitable for projects where requirements are not clear and contains high risk of changing. This model does not support iteration of phases. It does not easily handle concurrent events. Agile model: Agile model believes that every project needs to be handled differently and the existing methods need to be tailored to best suit the project requirements. In Agile, the tasks are divided to time boxes (small time frames) to deliver specific features for a release. Iterative approach is taken and working software build is delivered after each iteration. Each build is incremental in terms of features; the final build holds all the features required by the customer. Here is a graphical illustration of the Agile Model − Bikash Bista 2ndsem (HND) 16 SDLC The Agile thought process had started early in the software development and started becoming popular with time due to its flexibility and adaptability. The most popular Agile methods include Rational Unified Process (1994), Scrum (1995), Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic Systems Development Method (DSDM) (1995). These are now collectively referred to as Agile Methodologies, after the Agile Manifesto was published in 2001. Following are the Agile Manifesto principles − Individuals and interactions − In Agile development, self-organization and motivation are important, as are interactions like co-location and pair programming. Working software − Demo working software is considered the best means of communication with the customers to understand their requirements, instead of just depending on documentation. Customer collaboration − As the requirements cannot be gathered completely in the beginning of the project due to various factors, continuous customer interaction is very important to get proper product requirements. Bikash Bista 2ndsem (HND) 17 SDLC Responding to change − Agile Development is focused on quick responses to change and continuous development. Advantages of Agile Lifecycle model Is a very realistic approach to software development? Promotes teamwork and cross training. Functionality can be developed rapidly and demonstrated. Resource requirements are minimum. Suitable for fixed or changing requirements Delivers early partial working solutions. Good model for environments that change steadily. Minimal rules, documentation easily employed. Enables concurrent development and delivery within an overall planned context. Little or no planning required. Easy to manage. Gives flexibility to developers. Disadvantages of Agile Lifecycle model: Not suitable for handling complex dependencies. More risk of sustainability, maintainability and extensibility. An overall plan, an agile leader and agile PM practice is a must without which it will not work. Strict delivery management dictates the scope, functionality to be delivered, and adjustments to meet the deadlines. Depends heavily on customer interaction, so if customer is not clear, team can be driven in the wrong direction. There is a very high individual dependency, since there is minimum documentation generated. Bikash Bista 2ndsem (HND) 18 SDLC Transfer of technology to new team members may be quite challenging due to lack of documentation. Spiral Model: Spiral Model is a combination of a waterfall model and iterative model. Each phase in spiral model begins with a design goal and ends with the client reviewing the progress. The spiral model was first mentioned by Barry Boehm in his 1986 paper. The development team in Spiral-SDLC model starts with a small set of requirement and goes through each development phase for those set of requirements. The software engineering team adds functionality for the additional requirement in every-increasing spirals until the application is ready for the production phase. Planning phase:It includes estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the systemanalyst and the customer Bikash Bista 2ndsem (HND) 19 SDLC Risk Analysis: In this risk analysis, identification of potential risk is done while risk mitigation strategy is planned and finalized. Engineering phase: In this engineering phase, it includes testing, coding and deploying software at the customer site. Evaluating phase: This phase allows evaluation of software by the customer. Also, includes identifying and monitoring risks such as schedule slippage and cost overrum. Advantages of Spiral model: Changing requirements can be accommodated. Allows extensive use of prototypes. Requirements can be captured more accurately. Users see the system early. Development can be divided into smaller parts and the risky parts can be developed earlier which helps in better risk management. Disadvantages of Spiral model: Management is more complex. End of the project may not be known early. Not suitable for small or low risk projects and could be expensive for small projects. Process is complex Spiral may go on indefinitely. Large number of intermediate stages requires excessive documentation. Part 2: You are required to produce a document that explain the purpose of the feasibility report and describe how technical solutions can be compared. Bikash Bista 2ndsem (HND) 20 SDLC “A feasibility study is a preliminary study undertaken before the real work of a project starts to ascertain the likelihood of the project's success. A feasibility study is defined as an evaluation or analysis of the potential impact of a proposed project or program. A feasibility study is conducted to assist decision-makers in determining whether or not to implement a particular project or program. The feasibility study is based on extensive research on both the current practices and the proposed project/program and its impact on the selected organization operation. The feasibility study will contain extensive data related to financial and operational impact and will include advantages and disadvantages of both the current situation and the proposed plan. Purpose of feasibility study The importance of a feasibility study is based on organizational desire to “get it right” before committing resources, time, or budget. A feasibility study might uncover new ideas that could completely change a project’s scope. It’s best to make these determinations in advance, rather than to jump in and to learn that the project won’t work. Conducting a feasibility study is always beneficial to the project as it gives you and other stakeholders a clear picture of the proposed project. Some of the main purpose for conducting feasibility study are listed below: Improves project teams’ focus Identifies new opportunities Provides valuable information for a “go/no-go” decision Narrows the business alternatives Identifies a valid reason to undertake the project Enhances the success rate by evaluating multiple parameters Aids decision-making on the project Identifies reasons not to proceed This is done through feasibility study. In this various aspects like whether it is technically or economically feasible or not. So depending upon the aspect on which feasibility is being done it can be categorized into five classes: Bikash Bista 2ndsem (HND) 21 SDLC i. Technical Feasibility This assessment focuses on the organization's technical resources. It helps organizations determine if resources meet capacity and if the technical team can convert ideas into working systems. ii. Economic Feasibility This assessment typically involves a cost/benefits analysis of the project, helping organizations determine the viability and benefits associated with a project. iii. Operational Feasibility This assessment involves undertaking a study to analyze and determine whether -and how well- the organizations needs can be met by completing the project. iv. Legal Feasibility This assessment investigates whether any aspect of the proposed projct conflicts with legal requirements like zoning laws, data protection acts, or social media laws. v. Scheduling Feasibility This assessment is the most important for project success. In scheduling feasibility, an organization estimates how much time the project will take to complete. Comparison of Technical Solution: Technical solution has the purpose of planning, creating and implementing requirements solution. The technical solution should be contrasted with the feasibility study as the feasibility study is carried out for the right decision and the technical solution is the solution with the correct decision that will render the business / project profitable.Having the technological solution in the project will lead to an improvement in the project's result, so that it is included in the project. Some of the factors affecting the technical solution include: Reliability/Scalability: This includes multiple comparisons that offer the impression of a more reliable product. Reliable products are more considerate Scalability can also be considered, and we can find more scalability and reliability of products. Bikash Bista 2ndsem (HND) 22 SDLC Availability: Another can consider whether or not the product is correct according to his / her requirement. The quality of the commodity can be determined when compared with the requirement. Long life and extendable: It falls under the evaluation of whether the technologies can be expanded to meet the new requirements that are expected or not over the next few years. The new program to be created by the insurance provider needs to be practical and expanded to accommodate changes. Prescriptive: This investigates whether or not technology makes clear the correct tasks that must be performed. The new services the insurance provider offers are simpler for the consumers to use, fund and enforce. Conclusion: Hence, the study of feasibility is very critical to the development of software. The feasibility analysis also helps to ensure the product's necessity and efficiency. The time, costs and plans can be pre-discussed with the aid of feasibility study before the software development process. The feasibility analysis will also define defects and rectify them using different approaches such as technical solutions. P3: Undertake a software development lifecycle 1. Using appropriate software analysis tools / methods to do a software assessment and make a supporting documentation to perform the software review to satisfy the business need. This role may Bikash Bista 2ndsem (HND) 23 SDLC be provided in the form of a report organized with background details, reasons for problem, method for collecting data and description etc. In order to do system review, you need to distinguish the stakeholder, recognize the customer's prerequisites, indicate the extensions such as data sources, output, process and procedure descriptors, consider alternative arrangements and security consideration, and the quality confirmation that you have applied. Furthermore, you are expected to differentiate the imperatives such as costs, organizational strategies, legacy structures, and hardware prerequisites etc. You can use the following tools for software exams: Data flow diagram up to second level Entity Relationship Diagram 2. Reference to the above task that required some degree of focused research work investigate how needs for software can be tracked over the life cycle of the software. 3. Examine the distinctive ways of dealing with enhancing software quality in view of the above context discussing two approaches that can be applied to enhance software quality in this context. 4. Ultimately evaluate how use of the feature design model in the life cycle of the software development can enhance the quality of the product. Share your views on the mission you have done. Introduction: In this section, the researcher will make a report to support the software analysis to satisfy the business need of the insurance firm, the analyst will add background data, issue proclamations, data collection procedure and description and so forth. In the paper, uses of programming research tools, and use of SDLC to carry out the prerequisites will be referenced. Extra to this, the analyst will Bikash Bista 2ndsem (HND) 24 SDLC determine the various programming quality assurance approaches which are employed to improve the quality of the software. “At PPM, we provide those involved in investigation management, security, and risk with the best incident management tools to improve their business processes. Part of our ethos is also sharing information related to the company with those involved in it. With this ongoing commitment in mind, we have invited John Buckley to share his insights about how professionals can efficiently handle investigations. Defining Investigation Management On being asked to write about investigation management, my first thought was — that is not a question. My second thought was — what do you mean by investigation management? And my third thought was — Google must have an response! Except it doesn't have an answer, five pages in and no indication of a description of any practical usage. I started to wonder where to go next and how many others would find themselves in the same position? How will we discuss anything if we do not have a common understanding of what we are discussing? Investigation management is a concept that has arisen in the past number of years when both the public and private sectors understand that if they want to make their companies work more efficiently, and in the case of the private sector, more profitably, then things that have gone wrong, were going wrong, or could go wrong in the future, need to be investigated. Particularly in law enforcement where inquiries have been taking place for decades, the word ‘investigation management’ is arguably not in common use. As the clients are extended in the organization, the structure in the organization ought to be modified by which the customers could be dealt with effectively. As the organization is setting off to the few different nations, there may be diverse type of monetary forms to bargain with. Also the organization should manage the diverse sorts of individuals having distinctive culture and distinctive behavior. For upgrade the framework of the insurance firm we are going to need a new software program with many more features in it. Required features in the new software The new structure on the enterprise will become increasingly stronger and simpler for the consumers of the different nations to recognize, and will be able to handle the various types of currencies anywhere in the world. The company user will most certainly alter the software's language support.The second point is that the commodity should probably be handled with different monetary forms from different nations and, therefore, the estimates of the distinctive monetary forms will Bikash Bista 2ndsem (HND) 25 SDLC almost certainly be transformed on the grounds that the calculation of different monetary norms is unique. The company will almost certainly be making the transaction with the various normal currencies. The company is growing big as the group is expanding everywhere in the world. Making the easy to understand program won't just have the capacity to keep the data checked and up to date.Interestingly, the company should almost certainly handle different currency standards from different nations and moreover the estimates of the different currencies should most definitely be transformed from the fact that the measurement of different currency standards is special. The asset most certainly will be making the transaction with the different monetary types. The key concern about the software is that additionally the software needs to be fundamentally secure. More hazards and threats exist for the high calculation of data in the program 's server. The information protection framework will also be extended to deal with the threats and dangersIf anyone hacked the organization's information it can lead the organization to a huge misfortune at that level. The other basic requirement and condition for the program at that stage is that it will have to retain all of the client 's data. It should also have highlights to document their transaction as well. If the company is the insurance provider, the program will most certainly document that the policy has been taken by the client for how long.What's more, how much cash the client had paid. It should also have the capacity to keep track of whether the customer has paid their installment on time. If not, then what should be finished? The organization is going to be global so it should also have the android application with the goal that the customer could use the application to view their full record dataAdditionally, the customer will be allowed to pay the insurance payment from their home with the help of the app or with the help of the mobile wallet that will save the customer's time. Additionally, we realize that the insurance agency will have a lot more customers who have account.Along these lines, finding that if the client has paid the installment is going to be problematic in the colossal rundown and an auto identification could be included in the program that could identify the client that did not pay the installment on that date. It would be increasingly efficient to hold all clients records and monitor their status. Planning of the software Bikash Bista 2ndsem (HND) 26 SDLC Selection of the software development lifecycle model As to the needs of the insurance agency and to fulfill any requirement of the insurance agency, the software needed for the company has far more prerequisites. Currently focusing on those prerequisites of the software , making this software would be a huge project. Thus, to make this software we must follow the spry model which is one of the important software lifecycle advancement modelThere is a reason for picking this spry model to build this product. The key reason for choosing this model is that the agile model is ideal for this kind of extremely gigantic project in which incredibly high demands are imposed. There are also a lot of needs in this project which can not be recognized at the beginning.In case we need to create the little project or program, we 'd select the software development models like the waterfall model or the V model that's right for the little project at this stage. In either case we need to follow the agile model because of our expansive project. Using appropriate software analysis tool The tools or systems that help the software code 's fundamental functioning, screen the software 's conduct while running, and provide insight into the application's execution history is known as the information analytics tool or techniques.We are currently using the appropriate software inspection tool to accelerate the advancement process, improve the efficiency of the software, and optimize for optimal performance. Software coverage, instruction follow, memory test and performance review are the program analysis tool that we will be using to develop our program.We will use the code coverage to calculate the measurement of the executed program, follow the instructions to record exactly what happens when executing the code,Memory inspection to monitor the memory use of the code and to discern possible errors, finally we will use performance analysis to identify performance bottlenecks and other issues that allow the program to be modified for higher performance. Design of the software Data flow diagram of the software Here is the software data flow diagram which we will create for the insurance business. Bikash Bista 2ndsem (HND) 27 SDLC We can get the whole thinking about how the app would work in this chart. The data flow chart above provides the basic thought on what the work procedure is within the program. The figure similarly gives the software's internal structureThis should be obvious in the figure that when the client pays the amount or makes the installment for the defense at first the information is gone into the database then the information is treated in the database then the information about the client is reviewed and the information is put on the client's record after the validation. The transaction happens at that stage.The transaction information is prepared and stored in the database again at that point. And once again, the customer's information seems to indicate that the payment has been made and the customer will be secured. Entity relationship diagram Bikash Bista 2ndsem (HND) 28 SDLC The figure shown above is the relationship chart item that indicates how the information is located within the database. This provides clear analysis of the software's database structure. There are 2 client and account components in the database. The client has two characteristics which are name and age, and the record also has two assets which are time and balanceIn addition, a similar relationship has been formed between these two elements to interface the data of those two elements. Conclusion I have created a report in this section to seek the program test to satisfy the insurance agency's business needs. The analyst must integrate context data, problem proclamations, method of data accumulation and description, and so on, into this article.Until carrying out the analysis, however, it is important to consider collaborators, consumer prerequisites, scope such as knowledge sources, yields, procedures, and project value affirmation. This item will likewise be included in this study along these lines.Similarly , the study will discuss the use of software review tools, and the use of SDLC to fulfill the prerequisites. The scientist should define, in addition to these, the distinctive software quality assurance approaches that are used to improve software quality.In addition, I have also addressed the functionality of the present program and its limitation in this assignment. Bikash Bista 2ndsem (HND) 29 SDLC PART IV: SUITABILITY OF SOFTWARE BEHAVIOURAL DESIGN TECHNIQUES 1. Set up a documentation that clarifies how client and software prerequisites have been tended to. You may arrange this task with the segments that has the normal customer necessities and the genuine output of the item to be developed after the proper investigation. 2. Examine about the different software particular methods and propose two software behavioral specification techniques and outline their utilization with a model significant to the project that should be developed for the given context. A portion of the software particular procedures incorporate flowcharts, pseudo code and formal detail techniques, etc. 3. Separate between a finite state machines (FSM) and an extended Finite State giving an application to both. 4. Present justification of how information driven software can enhance the unwavering quality and adequacy of the software. The program we've created has all the part that our insurance provider needs. It calls for a lot of resources as the insurance company. Moreover, it is also a worldwide company so that the need for need rises againDue to the intense importance of the insurance agency's requirement and concentrating on every single need of the universal market insurance business the task of creating the software for that insurance agency was an extraordinarily huge project. Suitability of the software We made the program in using agile lifecycle display as we witnessed all the need. This model of the lifecycle was incredibly useful for our project, as it was extremely huge and the needs were constantly updated and added. The program is designed in such a way that it can hold each of the clients' records that pay the payment in order to receive the protection and also hold each of the transaction records that were made in the insurance company.In addition, the program also keeps the customer's near to personal details in the records as customers offer in the form some of their details. The program records the client's measure of installment and also provides the details that the client should be secured. Furthermore this program approves the application and checks whether the application is fake or notIt also checks whether or not the client has paid the cash sum, and offers the premise. These can also list the consumers who have not paid the installment on time so that the insurance provider can Bikash Bista 2ndsem (HND) 30 SDLC locate the customer who has not made the installment and can consult with them about their services without much effort. Our program was designed in such a way that it could accommodate its complex language and currency with the company around the globe. The distinctive sort of cash handling is a standout among the best part of the program. Because the cost of currency changes every day, the program will be equally able to adjust the amount of cash relative to pound sterling.Another primary component of the commodity is the modification of the different nations' distinctive language. As the organization is developing all the representatives and customers at the specific language couldn't work away. So that characteristic is given. All of Insurance Company’s vital requirement has been fulfilled in holding this part on this program.In fact, the app is genuinely accommodating and has a nice requirement for the consumer to use. The software has a greater number of features than required by the Insurance Company or some other organization around the globe. In this respect, I feel that on this program both the company and the insurance agency requirement has been tended to. Conclusion: By this way, the program is supervised and designed in a way that embraces multiple language numbers so that consumers can make purchases on the different monetary types. If we make these apps available to customers, the company, staff and customers would benefit. Bikash Bista 2ndsem (HND) 31 SDLC References Anon., 2019. Jobsite. [Online] Available at: https://jobsite.procore.com/data-driven-software-raises-the-game [Accessed 3 Jan 208]. Anon., 2019. Wikipedia. [Online] Available at: https://en.wikipedia.org/wiki/Data-driven_programming [Accessed 4 Jan 2018]. Bikash Bista 2ndsem (HND) 32