Please enable JavaScript.
Coggle requires JavaScript to display documents.
Lecture 5 (Design Concepts) (Design and Quality ((Quality Guidelines…
Lecture 5 (Design Concepts)
Data Object
Representation of any composite information must be understood by software.
Description of data object and attributes
Data object encapsulates data only
Can be :-
External entity(produces consumes information)
A thing(a report)
A role(salesperson)
An occurrence(telephone call)
An organizational unit(accounting dept)
A place(warehouse)
A structure(File)
A data object contains a set of attributes that act as an aspect, quality, characteristics or descriptor pf the object
Architectural Description Language(ADL)
Provides semantics and syntax for describing software architecture
Designer ability to=
-Decompose architectural components
-compose individual components to larger arch blocks
-Represent interfaces
Architecture Reviews
Assess ability of software to meet systems quality requirement and identify potential
Reduce project costs by detecting design problems
Experience based, prototype and scenario and checklist
Agility and Architecture
To avoid rework, used to create and evole an architectural model
Allow software architects contributing to evolving storyboard
Agile projects delivery work products during each sprint
Reviewing code useful form architectural reviews
Design Software
analysis model -> design model
design representations -> data design, architectual design, interface design, component- level design.
Software Engineering Design
Data class
Architectural Design
Interface design
Component-level design
Analysis model
class-based elements
behavioral elements
flow- oriented elements
scenario - based elements
Design and Quality
must implement all of the explicit
requirements
must be a readable, understandable
guide
should provide a complete picture of the software
Quality Guidelines
exhibit an architecture
-should be modular
contain distinct representations
lead to data structures that are appropriate
lead to components that exhibit independent functional characteristics.
lead to interfaces that reduce the complexity
be derived using a repeatable method
be represented using a notation
Functional Independance
Cohension (relative functional strength of a module)
Coupling (relative interdependence among modules)
Refactoring
redundancy
unused design elements
inefficient or unnecessary algorithms
poorly constructed or inappropriate data structures
design failure that can be fix for a better one
Place User Control
Define interaction modes
Provide flexible interaction
Allow to interruptible and undoable
Interaction to customized
Hide technical internals
direct design appear
OO Design Concept
Design classes
Inheritance
Messages
Polymorphism
Design classes
analysis classes -> entity classes
Boundary classes are develop during design to create interface
Controller classes
creation or update of entity objects
instantiation of boundary objects as they obtain information from
entity objects
complex communication between sets of objects
validation of data communicated between objects or between the user and the application.
Design Class Characteristics
Complete
Primitiveness
High cohesion
Low coupling
Interface Analysis
Interact with system through interface
Perform to do work
presented part of interface
environment tasks be conducted
Design Model Elements
Data elements
Architectural elements
Interface elements
Component elements
Deployment elements
Data Modeling
examines data objects
focuses attention
creates a model at the customer level
indicates data objects related
Evaluation Cycle
Interface design
Arcane
Poor Response
No context sensitivity
No guidance
Too much memorization
Lack consistency
Member
1141125335 - Muhammad Aiman Bin Adanan
1151203235- SITI NURSYAKIRAH BINTI AHMAD SAIFUL NIZAM
