Syd601 – assignment 1
- 1. SYD601 – ASSIGNMENT 1 PRESENTATION ON METHODOLOGY Illustrating how different OO tools & techniques are integrated within an information systems development methodology Due 7th September 2012 James Russell – 2011000500
- 2. OO SYSTEMS DEVELOPMENT OBJECTS & CLASSES • What is an object? – It is a thing in the computer that can respond to messages… • An object has structure because it has • Attributes • Methods • Object types are either: • User interface • Problem domain
- 3. OO SYSTEMS DEVELOPMENT OBJECTS & CLASSES • What is a class? • It can be a thing, concept or abstract. • Thing – physical; for example A customer • Concept – Idea; eg: Transaction • Abstract – It doesn’t actually exist in a system as a concrete class, doesn’t have an instance created. It’s a super class
- 4. OO SYSTEMS DEVELOPMENT PRINCIPLES • Principles represent a set of guidelines that help us to avoid “design flaws” • Open Close Principle: • Classes, Modules & functions are open for extension but closed for modifications • Interface Segregation Principle • Clients, should not be forced to depend upon interfaces that they don’t use • Single Responsibility Principle • A class should have only one reason to change
- 5. UNIFIED PROCESS PHASES • The four phases of the unified process: • Inception • Elaboration • Construction • Transition
- 6. UNIFIED PROCESS PHASES - INCEPTION • We need to develop a vision of where we see G.E.B heading with regards to it’s system. What we want to accomplish is: • Making the business case • Defining the scope • Produce a rough estimate for costs involved
- 7. UNIFIED PROCESS PHASES – ELABORATION • This is where we refine things, such as the Vision and Identity as we discussed at the start. • We start to design and implement your system – the core architecture & functions • Before, we produces rough estimates, now we’re refining them – producing more realistic estimates for costing's.
- 8. UNIFIED PROCESS PHASES - CONSTRUCTION • Easily the largest phase, the remainder of the system is built on our foundational work in the Elaboration phase. • Ideally system features are implemented in a short series of time boxed iterations ( eg: We set aside 1 week to enable our DPS payment system has had enough time to be fully integrated into the system awaiting beta testing)
- 9. UNIFIED PROCESS PHASES - TRANSITION • Our beta is ready! • We complete the deployment, ensuring ample time to train staff on the use of the system and it’s functions. • Do we have feedback about the system? This is the time to apply subtle changes!
- 11. UNIFIED PROCESS DISCIPLINES • We have 6 main disciplines: • Business Modelling • Requirements • Design • Implementation • Testing • Deployment
- 12. UNIFIED PROCESS DISCIPLINES – SUPPORT DISCIPLINES • With 3 additional support disciplines • Project Management • Configuration & Change management • Environment
- 14. THE UML DIAGRAMS
- 15. UML STATIC MODELLING • Static view: it emphasizes the static structure of the system, using objects , attributes, operations & relationships. For example: A Domain Class Diagram
- 16. UML DYNAMIC MODELLING • The dynamic, or behavioural view – Emphasises the dynamic behaviour of the system by showing collaborations among objects, attributes, operations & relationships. The dynamic view includes: Sequence diagrams, or Activity diagrams Customer System Customer wishes to browse Category Browse Search Select Category ISBN Search Author Search Consult DB Return Results
- 17. INTEGRATION & PROJECT PLAN: • Integration • Version control (eg GEB_Usecase_v12) • Proposed timeline: • Scenario Methodology Due 7 th September • Progress Reports Due at key times • Scenario Documentation due 2 nd November • Process & Reflections due 8 th November
- 18. ENVIRONMENTS WE’RE USING: • MS Visio, Powerpoint, Word 2012 • Student UML • Modeliio • Google Docs
- 19. THANKS FOR LISTENING • James Russell – 2011000500 • Note on the work: All sources are a collaboration of Wiki, and Sandra’s powerpoints. As well as other websites. • No Space squirrels were harmed in the making or uploading of this ppt.