More Related Content
Recently uploaded (20)
Featured (20)
Software Engineering Process, Notation & Tools Introduction - Part 4
- 2. Table of Content Table of Content • Domains Of Interest • Systems Development Life Cycle • Software Development Life Cycle (SDLC) • IT Service Management (ITSM) • Model Driven Engineering • Object Oriented Software Engineering (OOSE) Coverage Coverage 2 SEPNT Introduction
- 3. 3 SEPNT Introduction • Relevant areas of interest in the Study or Application of any activity Domains Of Interest Domains Of Interest Concept Concept
- 4. 4 SEPNT Introduction • Critical Success Factors • Study & Application of Standards, historical Knowledge of Framework, Notation & Tools, for a Domain. Domains Of Interest Domains Of Interest Theory Theory
- 5. 5 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • People • Roles & Responsibilities • Architect • PM • Programmer • Others Domains Of Interest Domains Of Interest Theory Theory
- 6. 6 SEPNT Introduction Domains Of Interest Domains Of Interest Theory Theory
- 7. 7 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • Skills • Project Management • Engineering • Technology • ITIL • Others Domains Of Interest Domains Of Interest Theory Theory
- 8. 8 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • Structure • Span Of Effect & Control Domains Of Interest Domains Of Interest Theory Theory
- 9. 9 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • Strategy • Component Based Development • Platform Independent Design • Model Driven Engineering • Others • Styles • Strictness on Critical Path • Work From Home • Informal • Others Domains Of Interest Domains Of Interest Theory Theory
- 10. 10 SEPNT Introduction Domains Of Interest Domains Of Interest Theory Theory
- 11. 11 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • Shared Values • Behavioural • Non-judgmental Professional Communication • Empathy • Others Domains Of Interest Domains Of Interest Theory Theory
- 12. 12 SEPNT Introduction • Critical Success Factors • Software Engineering • Framework • Knowledge • Documents, Models & Code • Delivery Management • Products • Verticals • Engineering • Technology • Others Domains Of Interest Domains Of Interest Theory Theory
- 13. 13 SEPNT Introduction • Critical Success Factors • Software Engineering • Notation • Artefacts are coded or specified in a Standard language • Unified Modelling Language – OMG • OMT – James Rumbaugh • Booch – Grady Booch • Others Domains Of Interest Domains Of Interest Theory Theory
- 14. 14 SEPNT Introduction • Critical Success Factors • Software Engineering • Tool • Software Product used to create engineering Artefacts • Visual Paradigm - Free • Enterprise Architect - Sparx Systems • Rational Software Architect - IBM Domains Of Interest Domains Of Interest Theory Theory
- 15. 15 SEPNT Introduction • Examples • Manufacturing • Engineering • Scheduling • Budgeting • R & D • Software Engineering • Engineering • Technical Support • System Administration • Program Management Domains Of Interest Domains Of Interest Theory Theory
- 16. 16 SEPNT Introduction • Identify a few domains of interest for myABC To-Do To-Do Domains Of Interest Domains Of Interest
- 17. 17 SEPNT Introduction • Series of changes or transformation(s) from concept to realization to Maintenance of a System. Systems Development Life Cycle Concept Concept
- 18. 18 SEPNT Introduction • A process for Planning, Creating, Testing, Deploying, Maintaining Systems and associated / supporting People, Processes, Information & Systems. • Also involves training & deployment of People & Processes, Change Management, Organizational updates and other non-engineering activities. • The goal is to deliver high quality systems that meet or exceed customer expectations. • The process moves through a clearly defined lifecycle activity, within scheduled time-frames and cost estimates. Systems Development Life Cycle Theory Theory
- 19. 19 SEPNT Introduction • Example • Software Development Lifecycle (SDLC) • Software Testing Lifecycle (STLC) • Database Development Lifecycle (DDLC) Systems Development Life Cycle Theory Theory
- 20. 20 SEPNT Introduction • Identify a few Systems Development Life Cycle types for for myABC To-Do To-Do Systems Development Life Cycle
- 21. 21 SEPNT Introduction • A process for planning, creating, Testing, and deploying an Information System. Software Development Life Cycle (SDLC) Concept Concept
- 22. 22 SEPNT Introduction • Constitutes clearly defined work activities, used by Systems engineers and Systems developers to plan, Design, build, test, and deploy Information Systems. • A Framework which describes activities performed at each stage in the SDLC. Software Development Life Cycle (SDLC) Theory Theory
- 23. 23 SEPNT Introduction • Models • Waterfall • Spiral • Rapid Application Development (RAD) • Agile • Test Driven Development(TDD) • V-Shaped Model • Prototyping • Big Bang Model • Iterative Theory Theory Software Development Life Cycle (SDLC)
- 24. 24 SEPNT Introduction • Models • Waterfall • A sequential Design process • First described by Winston W. Royce in 1970 and Bell and Thayer in 1976 • Each successive lifecycle activity begins only when the predecessor ends Theory Theory Software Development Life Cycle (SDLC)
- 25. 25 SEPNT Introduction • Models • Waterfall • Advantages • Easy to understand and Apply • Simple • Good for management planning & tracking • Disadvantages • All Requirements must be known before proceeding to the next activity • Integration must be done in the end • Any issue/risk at any stage may require the cycle to be repeated / revisited, leading to wastage of resources. Theory Theory Software Development Life Cycle (SDLC)
- 26. 26 SEPNT Introduction • Models • Spiral • A sequential Design process • Described by Barry Boehm in 1986 • Adds risk Analysis and prototyping to the Waterfall Model Theory Theory Software Development Life Cycle (SDLC)
- 27. 27 SEPNT Introduction • Models • Spiral • Advantages • Early risk discovery • Early user view because of rapid prototyping • Early and frequent feedback from users • Timely assessment of costs • Disadvantages • Time for risk Analysis may be too high for low-risk projects • Complex skills maybe required for Risk Analysis Theory Theory Software Development Life Cycle (SDLC)
- 28. 28 SEPNT Introduction • Models • Rapid Application Development (RAD) • Prototyping and iterative Development with no specific planning involved but develop while you learn, with early user feedback. Theory Theory Software Development Life Cycle (SDLC)
- 29. 29 SEPNT Introduction • Models • Rapid Application Development (RAD) • Advantages • Early user view leads to early business level use of the System • Better cost management • Disadvantages • Dependency on end users • May lead to poor technical Design, by changing focus from technicals to functionality. Theory Theory Software Development Life Cycle (SDLC)
- 30. 30 SEPNT Introduction • Models • Agile • A methodology that promotes short & continuous iteration of development and testing throughout the software development life cycle of the Project. • Development and testing activities are concurrent • A group of software development methods in which solutions evolve through collaboration between self-organizing, cross-functional teams. • Promotes Adaptive Planning, Evolutionary Development, Early Delivery, Continuous Improvement and encourages rapid and flexible response to change. • Example • Extreme Programming (XP) • SCRUM • FDD (Feature Driven Development) Theory Theory Software Development Life Cycle (SDLC)
- 31. 31 SEPNT Introduction • Models • Agile Theory Theory Software Development Life Cycle (SDLC)
- 32. 32 SEPNT Introduction • Models • Agile • Advantages • Customer satisfaction by rapid, continuous delivery of useful software • People and interactions are emphasized rather than process and tools • Customers, developers and testers constantly interact with each other • Working software is delivered frequently (weeks rather than months) • Face-to-face conversation is the best form of communication • Disadvantages • In case of large software deliverables, it is difficult to assess the effort required at the beginning of the software development life cycle. • There is lack of emphasis on necessary designing and documentation • The project can easily get taken off track if the customer representative is not clear what final outcome that they want. Theory Theory Software Development Life Cycle (SDLC)
- 33. 33 SEPNT Introduction • Models • Test Driven Development(TDD) • Test cases are developed to specify and validate what the code will do • Test cases for each functionality are created and tested first and if the test fails then the new code is written in order to pass the test and making code simple and bug-free.. Theory Theory Software Development Life Cycle (SDLC)
- 34. 34 SEPNT Introduction • Models • Test Driven Development(TDD) • Advantages • Only needed code is written • Easier to maintain and refactor • High test coverage • Tests document the code • Disadvantages • Process is slow • Tests need to be kept in sync with requirements • All the team members need to do it Theory Theory Software Development Life Cycle (SDLC)
- 35. 35 SEPNT Introduction • Models • V-Shaped Model • Testing and development stages proceed in parallel • The testing stages correspond to development stages • Like in a waterfall model, the next stage doesn’t begin until the previous one is finished. Theory Theory Software Development Life Cycle (SDLC)
- 36. 36 SEPNT Introduction • Models • V-Shaped Model Theory Theory Software Development Life Cycle (SDLC)
- 37. 37 SEPNT Introduction • Models • V-Shaped Model • Advantages • Simple to use • Saves time • Proactive error tracking • Straight-forward design • Disadvantages • Limited flexibility • Risk prone • Not good for complex and object-oriented projects • Does not support iteration of phases Theory Theory Software Development Life Cycle (SDLC)
- 38. 38 SEPNT Introduction • Models • Prototyping Model • Process of developing a working replication of a product or system that has to be engineered. • It offers a small scale facsimile of the end product and is used for obtaining customer feedback • Used when the customers do not know the exact project requirements beforehand. • A prototype of the end product is first developed, tested and refined as per customer feedback repeatedly till an acceptable prototype is achieved that forms the basis for developing the final product. Theory Theory Software Development Life Cycle (SDLC)
- 39. 39 SEPNT Introduction • Models • Prototyping Model Theory Theory Software Development Life Cycle (SDLC)
- 40. 40 SEPNT Introduction • Models • Prototyping Model • Advantages • Flexible • Easy to detect errors • Scope of refinement • Ideal for online systems • Can actively involve users in the development phase • Disadvantages • Costly • Poor documentation • There may be too much variation in requirements • Higher customer delivery expectations • May be sub-optimal solutions because of developers in a hurry to build prototypes Theory Theory Software Development Life Cycle (SDLC)
- 41. 41 SEPNT Introduction • Models • Big Bang Model • Starts from nothing • Requires almost no planning • Requires lots of funds and coding and takes time • Combines time, efforts, and resources to build a product • The product is gradually built as requirements grow Theory Theory Software Development Life Cycle (SDLC)
- 42. 42 SEPNT Introduction • Models • Big Bang Model Theory Theory Software Development Life Cycle (SDLC)
- 43. 43 SEPNT Introduction • Models • Big Bang Model • Advantages • No planning required • Suitable for small projects • Few resources are required • Does not require managerial staffs • Easy to implement • Disadvantages • Not suitable for large projects • Highly risky model • Might be expensive if requirements are ambiguous • Unsuitable for continuous projects Theory Theory Software Development Life Cycle (SDLC)
- 44. 44 SEPNT Introduction • Models • Iterative • An iterative process starts with a simple implementation of a small set of the software requirements. • Iteratively enhances the evolving versions until the complete system is implemented and ready to be deployed. • Does not attempt to start with a full specification of requirements • Development begins by specifying and implementing just part of the software, that is reviewed to identify further requirements. • This process is then repeated, producing a new version of the software at the end of each iteration of the model. Theory Theory Software Development Life Cycle (SDLC)
- 45. 45 SEPNT Introduction • Models • Iterative Theory Theory Software Development Life Cycle (SDLC)
- 46. 46 SEPNT Introduction • Models • Iterative • Advantages • Emphasis on accurate documentation • Resolution of project risks associated with client's evolving Requirements • Low risk of integration rework, as we integrate as we go along the SDLC • Development time required is less due to reuse of Components • Disadvantages • Team members need to be expert in their field • Development process is too complex and disorganized • Reuse of Components may not be possible, in certain cases Theory Theory Software Development Life Cycle (SDLC)
- 47. 47 SEPNT Introduction • Identify Software Development Life cycle Models for software engineering work for myABC. Software Development Life Cycle (SDLC) To-Do To-Do
- 48. 48 SEPNT Introduction • Information technology service management (ITSM) is the practice of planning, implementing, managing and optimizing the end-to-end delivery of information technology services to meet user needs and business goals.. IT Service Management (ITSM) Concept Concept
- 49. 49 SEPNT Introduction • The set of activities directed by policies, processes & procedures that are performed by an organization to Plan, Design, Deliver, Operate and Control IT services offered or provided to customers. IT Service Management (ITSM) Theory Theory
- 50. 50 SEPNT Introduction IT Service Management (ITSM) Theory Theory
- 51. 51 SEPNT Introduction • Frameworks • ITIL (Information Technology Infrastructure Library) • A set of comprehensive practices for ITSM that focuses on aligning IT services with business. • Processes, procedures, tasks, and checklists that are not organization or technology specific. • Enables an organization to establish a baseline to plan, implement, and measure. • Used to demonstrate compliance and to measure improvement Theory Theory IT Service Management (ITSM)
- 52. 52 SEPNT Introduction • Frameworks • ITIL (Information Technology Infrastructure Library) • UK Government's Central Computer and Telecommunications Agency (CCTA) in the 1980s developed a set of recommendations in response to growing IT requirements. • CCTA recognized that, without standard practices, government agencies and private companies had started independently creating their own IT management practices. • ITIL originated as a collection of books, each covering a specific practice within IT service management. • ITIL was built around a process model view of controlling and managing operations often credited to W. Edwards Deming and his plan-do-check-act (PDCA) cycle. • ITIL evolved from Ver 1.0 (1980s) to Ver 4.0 (2019) Theory Theory IT Service Management (ITSM)
- 53. 53 SEPNT Introduction • A Software Development Methodology which focuses on creating and exploiting Abstract representations of the Knowledge and Activities that govern a particular Application Domain, rather than on the Computing concepts. Concept Concept Model Driven Engineering
- 54. 54 SEPNT Introduction Theory Theory Model Driven Engineering
- 55. 55 SEPNT Introduction • Increases productivity by maximizing reuse across Systems, simplifying the process of Design. • Promotes communication between Individuals and Teams working on the System (via Standardization of Terminology and Best Practices used in the Application Domain). • Effective if Models • Make sense from the point of view of a user that is familiar with the Domain, and if they can serve as a basis for implementing Systems. • Are developed through extensive communication among Product Managers, Designers, Developers and Users of the Application Domain. • As Models approach completion, they enable the development of Software and Systems. Theory Theory Model Driven Engineering
- 56. 56 SEPNT Introduction • Process • PIM • Platform Independent Model(ing) • PSM • Platform Specific Model(ing) • MDA • Model Driven Architecture Theory Theory Model Driven Engineering
- 57. 57 SEPNT Introduction Target – Single Database for Origination & Customer Service • Object-oriented Software Engineering (commonly known by acronym OOSE) is a Software Analysis, Design, Programming & Testing Process, Notation & Tooling that employs Objects. • The first object-oriented design methodology to employ Use cases to drive software design. • The first object-oriented design methodology to employ Use cases to drive software design. • Developed by Ivar Jacobson in 1992 • OOSE is one of the precursors of the Unified Modelling Language (UML). • Includes a requirements, Analysis, Design, an Implementation and Testing model. Object Oriented Software Engineering Object Oriented Software Engineering Concept Concept
- 58. 58 SEPNT Introduction Target – Single Database for Origination & Customer Service • History • 1960-70 • The first object–oriented language was Simula (Simulation of real systems) that was developed in 1960 by researchers at the Norwegian Computing Center. • 1970-80 • Alan Kay at Xerox PARK created a personal computer named Dynabook and the first pure object-oriented programming language (OOPL) - Smalltalk, for programming the Dynabook. • 1980-90 • Grady Booch published a paper titled Object Oriented Design that mainly presented a design for the programming language, Ada. • He extended his ideas to a complete object–oriented design method Object Oriented Software Engineering Object Oriented Software Engineering Theory Theory
- 59. 59 SEPNT Introduction Target – Single Database for Origination & Customer Service • History • 1990 onwards • Coad incorporated behavioral ideas to object-oriented methods • Grady Booch invented the Booch method in 1991, a widely used method in object-oriented analysis and design. • The object-modeling technique (OMT) for software modeling and designing was developed in 1991 by James Rumbaugh as a method to develop object- oriented systems and to support object-oriented programming. • OOSE (Object Oriented Software Engineering) was developed by Ivar Jacobson in 1992. • First object-oriented design methodology that employs use cases in software design. • OOSE is one of the precursors of the Unified Modelling Language (UML), such as Booch and OMT. Object Oriented Software Engineering Object Oriented Software Engineering Theory Theory
- 60. 60 SEPNT Introduction Target – Single Database for Origination & Customer Service • History • 1990 onwards • Ivar Jacobson Model Object Oriented Software Engineering Object Oriented Software Engineering Theory Theory