ICT117 Week10 Model Validation S

Moving on to Design
Chapter 8: Dennis, Wixom and Tegarden
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition
Copyright 2009 John Wiley & Sons, Inc. All rights reserved.
Objectives
Understand the verification and validation of the analysis models. Understand the transition from analysis to design. Understand the use of factoring, partitions, and layers. Be able to create package diagrams. Be familiar with the custom, packaged, and outsource design alternatives. Be able to create an alternative matrix.
17/03/2011
ICT117 Systems Analysis & Design, Semester 2, 2010. Includes John Wiley & Sons material.
Key Ideas
The purpose of the analysis phase was to figure out what the business needs. The purpose of the design phase is to figure out how to provide it. The steps in both analysis and design phases are highly interrelated and may require much going back and forth i.e. iterative or spiral development
17/03/2011 ICT117 Systems Analysis & Design, Semester 2, 2010. Includes John Wiley & Sons material. 3
Avoiding Classic Design Mistakes

Reducing design time Feature creep Silver bullet syndrome Switching tools in mid-project
17/03/2011
VERIFYING AND VALIDATING (V&V) THE ANALYSIS MODELS
Walkthroughs
Peer reviews of models and diagrams that were created during analysis
Conducted by teams of analysts, designers, and clients Main purposes: Test the fidelity of the models Uncover errors or faults
Potential danger is that analysts may be criticised when the errors are uncovered !
Functional Model V&V

Events in Use Case descriptions should map to activities in the Activity Diagram Object node in an activity diagram must be mentioned in Use Case descriptions Sequential ordering within the Use Cases should match the ordering in the Activity Diagram There must be a one-to-one correspondence of Use Cases in the Use Case Diagram and Use Case descriptions.
17/03/2011
Functional Model V&V

All actors listed in a use case description must be portrayed on the use case diagram Include stakeholders listed in the use case description as actors in the use case diagram All relationships listed in a use case description must be portrayed on a use case diagram
Structural Model V&V

Every CRC card should be associated with a class on the class diagram Responsibilities listed on the CRC card must be operations in a class on a class diagram Collaborators on the CRC card imply some type of association on the class diagram Attributes listed on CRC cards must be attributes in a class on a class diagram

Class attributes with a type that is another class imply a relationship between classes Relationships on the CRC cards must show up on the class diagram Use association classes only if the association has unique attributes not on either class
17/03/2011
10
Behavioural Model V&V

Actors and objects on sequence diagrams must be included on communication diagrams Messages on sequence diagrams require associations on communications diagrams Every message on a sequence diagram must appear as a message on an association in the corresponding communication diagram Guard condition messages in sequence diagrams require equivalent guard conditions on the corresponding communication diagrams

The sequence number on message labels in communications diagrams must correspond to the top-down ordering of the messages being sent on the sequence diagram State machine transitions must be associated with a messages on sequence and communication diagrams All entries in a CRUD matrix imply a message being sent between an actor or object and another
17/03/2011
12
EVOLVING THE ANALYSIS MODELS INTO DESIGN MODELS
Factoring
Creating modules that account for similarities and differences between units of interest New classes Generalisation Aggregation Abstracting Refinement
17/03/2011
14
Partitions and Collaborations

Creating subsystems or larger units Grouping units that collaborate May have collaboration among units or partitions The more messages or contracts between objects, the more likely they are in the same partition
17/03/2011
15
Layers
Consider system environment information to help evolve the analysis model Model-view-controller (MVC) architecture Separating application logic from user interface logic
17/03/2011
16
5 Layers
Foundation Problem Domain Data Management Human-Computer Interaction Physical Architecture
17/03/2011
17
PACKAGES AND PACKAGE DIAGRAMS
Package
A general construct that groups units together Used to reduce complexity of models A package diagram shows packages only
17/03/2011
19
Package Diagram for 5 Layers
17/03/2011
20
Building Package Diagrams

Set the context Cluster classes together based on shared relationships Model clustered classes as a package Identify dependency relationships among packages Place dependency relationships between packages
DESIGN STRATEGIES
Custom Development
Allows for meeting highly specialised requirements Allows flexibility and creativity in solving problems Easier to change components Builds personnel skills May tax firms resources May add significant risk
Packaged Software
Software is already written May be more efficient May be more thoroughly tested and proven May range from components to tools to whole enterprise systems But clients must accept the functionality provided May require changes in how the firm does business May require significant customization or workarounds to support mandatory processes
System Integration
The process of combining packages, legacy systems, and new software Key challenge is integrating data Write data in the same format Revise existing data formats Develop object wrappers
17/03/2011
25
Outsourcing
Hire an external firm to create the system They may have more skills They may extend existing company resources Caveats: Never outsource what you dont understand Carefully choose the vendor Prepare contract and payment style carefully
Selecting a Design Strategy

Business need In-house experience Project skills Project management Time frame
17/03/2011
27
Selecting a Design Strategy

Use Custom Development when Business Need The business need is unique In-house functional and technical experience exists There is a desire to build in-house skills The project has a highly skilled project manager and a proven methodology Use a Packaged System when The business need is common In-house functional experience exists Use Outsourcing when The business need is not core to the business In-house functional or technical experience does not exist The decision to outsource is a strategic decision The project has a highly skilled project manager at the level of the organization that matches the scope of the outsourcing deal The time frame is short or flexible
28
In-house Experience
Project Skills
The skills are not strategic The project has a project manager who can coordinate vendors efforts
Project Management
Time frame
17/03/2011
The time frame is The time frame is ICT117 flexible Systems Analysis & Design, Semester 2, 2010. short
Includes John Wiley & Sons material.
DEVELOPING THE ACTUAL DESIGN
The Alternative Matrix

Combines several feasibility analyses into one grid Revisits technical, economic, and organisational feasibility
17/03/2011
30
Request for Proposals (RFP)

Description of the system you propose to be built Vendors, developers, service providers respond with proposals including how they will address needs as well as stating cost and time requirements.
17/03/2011
31
Summary
Verifying and Validating the Analysis Models Evolving the Analysis Models into Design Models Packages and Package Diagrams Design Strategies Developing the Actual Design
17/03/2011
32

ICT117 Week10 Model Validation S

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ICT117 Week10 Model Validation S

Diunggah oleh

Hak Cipta:

Format Tersedia

Moving on to Design

Chapter 8: Dennis, Wixom and Tegarden

Avoiding Classic Design Mistakes

VERIFYING AND VALIDATING (V&V) THE ANALYSIS MODELS

Functional Model V&V

Functional Model V&V

Structural Model V&V

Structural Model V&V

Behavioural Model V&V

Structural Model V&V

EVOLVING THE ANALYSIS MODELS INTO DESIGN MODELS

Partitions and Collaborations

PACKAGES AND PACKAGE DIAGRAMS

Package Diagram for 5 Layers

Building Package Diagrams

Selecting a Design Strategy

Selecting a Design Strategy

DEVELOPING THE ACTUAL DESIGN

The Alternative Matrix

Request for Proposals (RFP)

Anda mungkin juga menyukai