________________________Seminars| ________________________Seminars |
|
Effiziente Systementwicklung mit der Unified Modeling Language System- und Software-Architekturen Mastering the Requirements Process Objektorientierte Entwicklung Von Echtzeitsystemen
|
Complete Systems AnalysisComplete Systems Analysis is modern analysis: it integrates process and data modelling, as well as giving you a comprehensive strategy for building a complete, accurate and provable requirements specification. MSA gives you a complete version of the techniques used by most of today's CASE tools. How do you get the right requirements so that you can build the right software, and how do you know they are right when you have them? Today's large, complex systems make it harder than ever to find the correct requirements. Now there is an answer: Complete Systems Analysis has a proven track record for delivering the right requirements. It uses a comprehensive modelling approach to build a specification containing all the requirements. It uses events to partition the system, and integrates the event-response process with the essential data for the event. The integrated models have their inbuilt rules of correctness. Add to this the CSA technique for ensuring completeness, and you can be certain that you are specifying precisely the system you need.
Today's analysis is different To be effective, today's systems analyst must use today's techniques and strategies.
Systems Analysis The idea of modelling is not new. Almost every engineering discipline builds models to invent, and then to specify, the final system. And like any other engineering model, analytical models are readily understood by the people who are to implement the system.
But What Is Complete Systems Analysis? Complete Systems Analysis integrates the event-response model of the processes with the entity-relationship model of the stored data, and makes the data dictionary and mini specifications support both. This integrated requirements specification is demonstrably complete: Complete Systems Analysis cross checks the models to ensure that no part of the system is overlooked. Complete Systems Analysis has become today's analysis technique by responding to today's analysis needs:
Making Sense of the Opportunities The effectiveness of CSA's teaching methods means that you start using these analysis techniques in your own workplace right away.
Who Can Benefit by Acquiring These Skills? Users: The popularity of this course with the many users who have attended confirms its usefulness to anybody connected to systems work. Systems Designers & Programmers: Complete Systems Analysis training allows designers and programmers to get a thorough working knowledge of the specification process, and so play a larger role in software development. Project Managers and Team Leaders: Your instructor is always willing to demonstrate how to use the analysis models to make accurate estimates of implementation effort, as well as using the models for project control.
What Will I Learn? The course includes: A Modelling Approach to Analysis: Models are miniature representations of a real-life system. Systems analysts describe their systems using models which are more understandable, and more accurate than traditional specifications. This introduction explains how to use models to understand and specify your system. Data Flow Diagrams: These are introduced with an interactive session to model a familiar system. The data flow conventions are discussed as they occur in the modelling effort. Levelling: Levelling is a way of controlling complexity in the models. It lets the analyst begin with a broad overview, and then make a controlled descent into the details of the system. Data Dictionary: The data dictionary specifies the data that is used by the system. This section demonstrates how to build a data dictionary to support your analysis models. Systems Analysis Viewpoints: Models are not always an exact replica of the system. Some models are more useful if they show a "justified distortion" emphasising aspects of the system that are significant to the reader. Similarly, a model's viewpoint can filter out information which is, for the moment, irrelevant. Modelling Essential Functions: The essential functions are the "real" processing policy of the system: they exist regardless of any implementation. This section demonstrates how to use event-response models to find the essential functions. Modelling Essential Stored Data: The entity-relationship diagram models the system from the viewpoint of the data. This section shows how to use entity-relationship models to understand the policy of the system, and to specify the system's requirement for stored data. Completing the Essential Model: Analysis models, if they are to be at all useful, must show all of the requirements. In this section we demonstrate how you use CRUD tables and entity state models to ensure the integrity and completeness of your analysis specification. Mini Specifications: This section discusses how and when to specify the policy for each process. It teaches how to write structured language and other specification techniques. Adding New Requirements: New requirements happen throughout the life of a system. This section shows how to integrate new policy with the existing. It also shows how to use this procedure for system maintenance. Modelling the Environment: The implementation environment contains the hardware and software that is used to bring the requirements into the real world. This section shows how to specify the environment by building a model of the devices available for implementation. Allocating Requirements: This section covers the transition from analysis to design. We demonstrate how to allocate the essential functions to the appropriate implementation devices, thus deciding the system's architecture. Object-oriented Analysis: This section explains how object-oriented systems work, and how the Modern Systems Analysis techniques are used to build object-oriented systems. Reusing Analysis: Despite appearances to the contrary, there are great similarities and overlaps between systems. Here we discuss how analysis models are reused, and how this reuse adds to the productivity of the analysis effort. Modern Systems Development - Reprise: This is a review of the course to date. It gives students a further opportunity to see how the analysis activities and models fit together. In the workshop at the end of this section, the student experiences the whole of the course's teaching by building a complete set of analysis models using our fast-track strategy. Own Workshop: In this workshop, course members model a system from their own workplace. We do this as course members have found the practical experience of modelling real-life systems to be the most effective way to apply these analysis techniques to their own work. The Atlantic Systems Guild - the Source
of Systems Analysis The six guild principals are all world famous for their pioneering contributions to the art of systems analysis. Tom DeMarco started it all when he wrote Structured Analysis and System Specification. Steve McMenamin and John Palmer invented event-response modelling when they produced Essential Systems Analysis. Tim Lister's work in quality assurance and reuse has brought many projects in ahead of schedule and under budget. And now James and Suzanne Robertson bring you over a decade of their international experience in their outstanding course Complete Systems Analysis.
Materials and Course Duration The course runs for five days. All teaching sessions and workshops are held within normal working hours.
For more information ...
and the many others who are satisfied users of Modern Systems Analysis, please contact the Atlantic Systems Guild:
|
