11/6/2016

 Model Driven Design

 Rapid Application Development
 Prototyping
 Joint application development
 Information Engineering
System Designing
 SSADM (Structured systems analysis and
design methodology)
 Object Oriented approach

Janaka Jayasinghe

 Feedback both the specifications and the

 System designing, using modeling methods is prototype can be improved
known as model driven.  Steps
 Modeling methods ◦ Identify basic requirements
 Determine basic requirements including the input and
◦ UML output information desired. Details, such as security, can
◦ State diagrams typically be ignored.
◦ Use case diagrams ◦ Develop Initial Prototype
 The initial prototype is developed that includes only user
interfaces.
◦ Review
 The customers, including end-users, examine the prototype
and provide feedback on additions or changes.
◦ Revise and Enhance the Prototype

 Types of Prototyping  Top-down information systems development

◦ Throwaway prototyping approach.
 A model is developed and will be discarded rather than  Employs data models(ER diagrams, DFD)
improving to a final delivered software.
and process models for each business
◦ Evolutionary Prototyping
function or area
 A model is developed and will be improving to a final
delivered software.

Janaka Jayasinghe

1
 11/6/2016

 Techniques
 Modern Information systems development life ◦ Data flow diagramming
cycle approach ◦ Entity life histories
 Top-down approach for functional  Tools
decomposition in analyzing processes. ◦ CASE tools
◦ Workbenches
 Rather than the text based documents,
diagrams are used for documentations to
improve user understanding.
 More focus on data more than the process

 Feasibility study  Real world entities are studied as objects

◦ Investigate system requirements
 Combines data and processes into single
◦ Focus on cost benefit analysis
 Requirement analysis
entities called objects.
◦ Analyze current operations (DFD)
◦ Options of new system
 Requirement specification
◦ Data and processes in new system
◦ System specification document will produced
 Logical design
◦ Not focus on Technical or hardware
◦ User interfaces
 Physical design
◦ The logical structure is designed to physical design
◦ For example database specification. Janaka Jayasinghe

 Upper Case tools

◦ Tools use for system analysis phase tasks.
◦ Documenting tools
◦ Designing tools – Used to draw system models
◦ ER diagrams, Data flow diagram, Structure charts, Decision
Trees
 Lower Case tools
◦ Tools use for later in the development process, which is
after analysis & design tasks.
◦ Performance analysis tools - check memory usage and
performances
◦ Debugging tools- simulate transactions
◦ Testing tools – simulate transactions and data traffic,
measure performance
◦ Correctness checking tools – Check syntax errors
◦ Application build tools (Integrated development
environments)