2. SDLC MODELS • A number of SDLC models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize & stabilize.
3. IMPORTANT ACTIVITIES IN SDLC 1. PLAN 2. ANALYSIS 3. DESIGN 4. DEVELOPMENT 5. TEST 6. IMPLEMENT 7. MAINTAIN
4. PLAN DEFINE THE SYSTEM TO BE DEVELOPED SET THE PROJECT SCOPE DEVELOP THE PROJECT PLAN INCLUDING TASKS, RESOURCES, AND TIMEFRAMES
5. SYSTEM ANALYSIS GATHER THE BUSINESS REQUIREMENTS FOR THE SYSTEM SRS – SYSTEM REQUIREMENTS SPECIFICATIONS
6. DESIGN DESIGN THE TECHNICAL ARCHITECTURE REQUIRED TO SUPPORT THE SYSTEM DESIGN SYSTEM FLOW CHART
7. DEVELOP PROGRAM BUILD THE TECHNICAL ARCHITECTURE BUILD THE DATABASE AND PROGRAMS
8. TEST / QC WRITE THE TEST CONDITIONS PERFORM TESTING OF THE SYSTEMS QUALITY CHECK
9. IMPLEMENT WRITE DETAILED USER DOCUMENTATION PROVIDE TRAINING FOR THE SYSTEM USERS
10. MAINTAIN BUILD A HELP DESK TO SUPPORT THE SYSTEM USERS PROVIDE AN ENVIRONMENT TO SUPPORT SYSTEM CHANGES
11. THE COST OF FINDING ERRORS MONEY VS. SDLC STEPS 60 50 40 30 COST 20 10 0 PLAN DEVELOP MAINTAIN STEPS TAKE TIME TO PLAN AND DO COMPLETE SYSTEM ANALYSIS AND DESIGN
12.
13. IMPORTANT TERMS PROTOTYPING - SIMULATE SYSTEM POC – PROOF OF CONCEPT SIGN OFF – USER ACCEPTANCE TEST AND SIGNATURE ON THE INPUT / OUTPUT / PROOF OF CONCEPT PROJECT LEADER – PERSON IN CHARGE OF THE SOFTWARE TEAM
15. MIS FOR e-VERYONE • Banking & Finance • Energy & Utilities • Engineering • FMCG • Government bodies and Associations • Insurance and Investment houses • Media • Medical & Healthcare • Pharmaceuticals & Chemicals • Services • Telecommunications • Travel & Transportation services • Warehousing & Logistics SOFTWARE B USINES S OP TIMIZ A TIONIS A MUST F ORALL KI NDS O F B USINES S
16. A flowchart is a schematic representation of an algorithm or a process. Many software packages exist that can create flowcharts automatically E.G. CASE TOOLS
17. SDLC & DFD SDLC SOFTWARE DEVELOPMENT LIFE CYCLE DATA FLOW DIAGRAM NOTATIONS
18. DFD A data flow diagram illustrates the processes, data stores, and external entities in a business or other system and the connecting data flows EXAMPLE
19. C.A.S.E. • CASE is an acronym that stands for Computer-Aided Software Engineering • In simple layman terms, CASE is a tool which aids a software engineer to maintain and develop software.
20. WHY CASE TOOLS Architecture management: Model, design, and rapidly build SOFTWARE, systems, and computer applications programs Change and release management : Improve software delivery and lifecycle traceability, from requirements through deployment Software development management: Align projects for improved productivity and predictability Quality management: Ensure software functionality, reliability, and performance throughout development and production
21. PURPOSE OF CASE TOOLS SOFTWARE Many CASE tools not only output code but also generate other output typical of various systems analysis and design methodologies DATA FLOW DIAGRAMS (DFD) ENTITY RELATIONSHIP DIAGRAMS (ERD) USER DOCUMENTATION