Class4_AnalysisModeling_UML

Class4_AnalysisModeling_UML - System Models / Analysis...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
System Models / Analysis Modeling Represents Requirements in multiple dimensions to uncover errors , inconsistencies and missing information
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 - Where are We? Communicat ion  Planning  Modeling Const ruct ion Deployment   analysis  design code  t est project   init iat ion  requirement   gat hering estimating  scheduling  delivery  support   f eedback Analysis Modeling Analysis Modeling
Background image of page 2
Analysis Modeling Is the first technical representation of the system Is a mean for partitioning the requirements Uses text and diagrams to depict requirements for data, functions and  behavior Used to validate requirements 4 types of Analysis Modeling 1. Scenario based Shows the system from the users point of view 2. Flow-Oriented (Data flow based) How functions transform data objects 3. Class based (objects, attributes, and relationships) Defines objects, attributes, and relationships 4. Behavioral modeling (states, events) Defines the states of the system and important events 
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Requirements Analysis Requirements analysis  specifies software’s operational characteristics indicates software's interface with other system elements  establishes constraints that software must meet Requirements analysis allows the software engineer to: elaborate on basic requirements established during earlier requirement  engineering tasks build  models  that depict user scenarios , functional activities , classes  and their relationships , system and class behavior , and the flow of data   as it is transformed. 
Background image of page 4
A Bridge system  description analysis  model design  model Analysis Model must: 1. Describe what is the customer require 2. Establish basis for design 3. Define a set of requirements that can be validated
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 - System modelling System modelling helps the analyst to understand the functionality of the  system and models are used to communicate with customers. Different models present the system from different perspectives External perspective  showing the system’s context or environment; Behavioural perspective  showing the behaviour of the system; Structural perspective  showing the system or data architecture.
Background image of page 6
7 - Model types Data processing  model showing how the data is processed at different  stages. DFD Composition model  showing how entities are composed of other  entities. Architectural model  showing principal sub-systems. Classification model  showing how entities have common  characteristics.
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/07/2011 for the course CS 430 taught by Professor Kapoor during the Summer '08 term at Illinois Tech.

Page1 / 88

Class4_AnalysisModeling_UML - System Models / Analysis...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online