Software Development Life Cycle ; Unit # 7

Digital Connections. Software Development Life Cycle ; Unit # 7.

[Audio] Welcome to an overview of the transformative journey Enomy Finances is embarking upon in adopting a new software system. Our focus in this presentation includes: An analysis of software requirements traceability, Insights into the chosen SDLC model, Strategies for enhancing software quality, And the profound impact of our investigative processes on the overall software quality..

[Audio] Commencing with the overview of traceability, some specific steps and methods have been outlined in the forthcoming slides. Firstly, let's explore the benefits that traceability has brought to the Enomy Finances project. Traceability, defined as the capability to trace requirements both forward and backward in the development phase, Throughout the development phases, including Requirement Planning, Design, Implementation, Testing, Deployment, and Maintenance, traceability effectively manages and addresses all arising risks. Now, let's delve into each of these steps for a more comprehensive understanding. No 1 is Requirement, in the very first step the Interviews, surveys, or workshops are conduct to gather requirements from stakeholders. No 2 is Planning, Project plan is developed , Roles and responsibilities are being clearly define , Requirements Traceability Matrix (RTM) is established and the same goes for enomy finances. No 3 is Design, Detailed design documents are created , Version control for design documents is implemented each design component is linked back to the specific requirement it addresses..

[Audio] No 4 is Implementation, in this phase Coding practices are adopted to trace code back to the requirements, Version control systems are utilized to track changes ,Comments or annotations are incorporated in the code to reference relevant requirements. Step no 5 is Testing, in this step Set of test cases based on the identified requirements or Testing tools are used , The results of each test case are documented and tracked. The Next step is Deployment, this phase focuses on validating the software, recording any configuration changes, and providing updated documentation to end-users, ensuring a successful transition from development to actual usage. The Maintenance phase involves implementing a structured change management process for software modifications, conducting impact analyses to understand the effects of requirement changes, and maintaining an audit trail of these changes for transparency and accountability..

[Audio] Now Lets Move to the model details used For the Enomy Finances, The chosen model in Software development life cycle is Agile. Agile is a flexible and iterative software development methodology that emphasizes collaboration, adaptability, and customer satisfaction. It is characterized by incremental progress, frequent reassessment, and continuous delivery. The reasons for choosing Agile for the Enomy Finances project may include:.

[Audio] Flexibility & Adaptability ,Agile allows for changes during development, vital for dynamic projects. Customer Involvement , Regular feedback ensures alignment with customer expectations. Quick Delivery , Short cycles lead to faster releases, delivering value sooner. Collaborative Approach Cross-functional teamwork for efficient development. Risk Reduction , Early issue identification minimizes project risks. Continuous Improvement, Regular retrospectives foster a culture of ongoing refinement. Enhanced Transparency, Daily stand-ups and reviews provide clear project visibility..

[Audio] Here is the graphical presentation of Agile model stages and iterations..

[Audio] Next, exploring the approaches used to enhance the software quality of newly developed financial software for enomy finances. Software quality is the extent to which a product meets requirements and satisfies user needs. It includes attributes defining excellence, reliability, and effectiveness. Ensuring high software quality is vital for optimal performance, defect-free functionality, and meeting user expectations. For the improved software quality the use techniques in the Report are Data Flow Diagram and Use Case Diagram. Data Flow Diagram: Visual representation of how data flows within a system. illustrating how inputs are transformed into outputs through processes. commonly used in software engineering and systems analysis to model and describe the structure and behavior of a system..

[Audio] Components of DFD : Processes Operations or transformations within the system, often depicted as circles or ovals. Data Flows Arrows showing the movement of data between system components—processes, data stores, and external entities. Data Stores Storage locations within the system, typically represented as rectangles. External Entities Sources or destinations of data outside the system, including other systems, users, or interacting entities..

[Audio] Diagram showing the Level 1 Data Flow of enomy finances..

[Audio] Use Case Diagram: Another method used in the solution is use case diagram to improve software quality. It is Visual representation of the functional requirements of a system from the perspective of its users. Use Case Diagram Used : Below is the use case diagram used in the task solution..

Approaches to Improve Software Quality. All of the use cases of database Record Transactions Log Diagnostic Data Cache User Data erate Reports depend on queries will perform these operations if only queries (triggered by event listeners) are run Handle user Authorization Store User Information Keeps Update Currency Exchange Rates Manage Account Balances Handle user Authentication Database Enomy Finan Administration Give Accesses and perm Configure Currency Handle System Errors Manage User Monitor System Performance Audit System Activities Generate Reputs Configure System Settings update System nage Savings an Investments Data.

Approaches to Improve Software Quality. Fill Forms Collect E-Receöts View Notifications View Investment Access Help and Support Perform Currency Conversion Can do changes in Profile Settings Request for transaction Request to initiate saving and investment plans Initiate Savings and Investments clients Access Help and Support Queries Provide financial Verity Details of the Clients Couect forms Assist Clients via System Customer Service live Chat functionality Manage investment portfolio Send transaction Statements on demand of client.

[Audio] Flow Charts , Visual representation that illustrates the sequence of steps, decisions, and processes in a system, making them a valuable tool in various stages of the Software Development Life Cycle (SDLC). The flow charts used in the SDLC are given below along with the brief explanation. 1st is the Flow chart Displaying Converted Currency.

Suitability of chosen software behavioral design techniques.

Suitability of chosen software behavioral design techniques.

Suitability of chosen software behavioral design techniques.

[Audio] Please enlarge the scale of the screen or zoom in for clearer view.