2. CONNECTING COMPONENT Pertemuan 23-24 Matakuliah: M0126 - Analisis dan Perancangan Sistem Informasi Lanjut Tahun: 2009 - 2010

3. Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Mahasiswa dapat menyusun kembali hasil analisis dan desain dalam sebuah dokumentasi (C5)

4. Outline Materi Mahasiswa dapat menyusun kembali hasil analisis dan desain dalam sebuah dokumentasi (C5)

5. Documentation Purpose To retain results and decisions in a coherent manner Concepts –Analysis document : A coherent presentation of the analysis results – Design document : A coherent presentation ofthe design results 17 – 18 / 02 - 13

6. Model Component (Cont’d) Principles –Use technical prose supplemented with formalisms –Retain results and decisions continuously –Chart progress through documented results Result –An analysis document –A design document 17 – 18 / 03 - 13

7. Importance of Documentation In system development, documents play a central role and serve different needs, acting as : – Work tools that collect and structure sub-results as they are produced – Control tools to measure work progress – Tools that retain agreements about system requirements and design 17 – 18 / 04 - 13

8. Template for an Analysis Document 1.The Task. Brief description of the document’s background and relationship Purpose. The overall intent of the system development project System Definition. Summary of the system’s overall properties. Context. Description of relevant aspects in the surroundings. Can include rich pictures, among other things. Problem Domain. Informal presentation of central phenomena in the system’s problem domain Application Domain. Informal presentation of the actors and work tasks 17 – 18 / 05 - 13

9. Template for an Analysis Document (Cont’d) 2.Problem Domain. Descriptions of classes, structure, and dynamics in the object system Clusters. Cluster structure Structure. Class diagram comprising generalization, aggregation, and association structures Classes. The classes are described individually. For each class, provide a description of : Definition. Brief characteristic of the class’ objects Behavioral Pattern. This can be described, for example, using an annotated statechart diagram Events. Event table and sequence diagrams for relevant common events 17 – 18 / 06 - 13

10. Template for an Analysis Document (Cont’d) 3.Application Domain. Complete description of usage, functions, interfaces, and other requirements of the system Usage. Description of the system’s interaction with the surroundings. Overview. Actor table that shows which actors and use cases are involved in the interaction Actors. Actor specifications for all actors Use Cases. Use-case specifications or statechart diagrams for all use cases Functions. Description of the system’s functionality. Complete Function List. List of all functions, including a function type and complexity assessment for each one Specification of Functions. Complex functions specified in relevant detail User Interface. Coherent presentation of central requirements to the system’s user interface Dialogue Style. Description of the basic style of presentation and dialogue and a complete list of elements in the user interface Overview. A navigation diagram of the total user interface Examples. Annotated examples of the user interface The Technical Platform. Outline of the technical platform and interfaces to other systems and devices 17 – 18 / 07 - 13

11. Template for an Analysis Document (Cont’d) 4.Recommendations. Argumentation for the ensuing development work. The System’s Usefulness and Feasibility. An assessment of the requirements’ relation to the surroundings and the technical possibilities Strategy. Recommended strategy for the ensuing development work Development Economy. Estimate for resource and time consumption in the ensuing development work 17 – 18 / 08 - 13

12. Template for a Design Document 1.The Task. Brief description of the task and the formulated quality goals Purpose. The overall intent of the system development project Corrections to the Analysis. Error corrections, necessary modifications, and supplements to the analysis document Quality Goals. The summary of prioritized design criteria and supplementary goals for the architecture 17 – 18 / 09 - 13

13. Template for a Design Document (Cont’d) 2.Technical Platform. Brief description of the design language and of equipment, system software, and systems on which the system id developed and realized Equipment. Description of relevant equipment System Software. Description of relevant system software System Interfaces. Description of the interface to systems that the system will interact with Design Language. Description of the applied design language with reference to familiar languages and standards 17 – 18 / 10 - 13

14. Template for a Design Document (Cont’d) 3.Architecture. Description of the system’s structuring into components and process. Including description of standards for architectural design Component Architecture. Commented class diagram showing the system’s structuring into related components Process Architecture. Deployment diagram showing the available processors, the active objects, and their connections Standards. Applied design standards 17 – 18 / 11 - 13

15. Template for a Design Document (Cont’d) 4.Components. Description of the model, function, system interface, user interface, and other components. For each component, provide a description of : Structure. Class diagram that describes the component’s classes, their structural relations, as well as the names of their attributes and non-trivial operations Classes. The classes are described to the extent that it is necessary and is not already apparent from structure. The class’ name Brief description of the class’ responsibility and purpose Attributes (using a list format) Complex operations, using operation specification Statechart diagram to describe the class’ behavioral pattern 17 – 18 / 12 - 13

16. Template for a Design Document (Cont’d) 5.Recommendations. A substantiated plan for the ensuing development work The System’s Usefulness. An overall evaluation of the design’s relation to the context based on the posed quality goals Plan for Initiating Use. Recommended plan for how the system is put into use Implementation Plan. Recommended plan for the system’s realization comprising activities and estimates of time and resource consumption. Perhaps just a reference to the relevant project plan 17 – 18 / 13 - 13