SYSTEM DESIGN the specification of a detailed computer-based solution focus is on the technical and/or implementation aspects of the solution

on specifies how the system will function models and approaches are methodolo y-based Typical desi n components! architectural desi n data desi n interface desi n output desi n procedural desi n pac"a e desi n #utput Desi n classification accordin to distribution! internal reports $ support day-to-day business operations% mana ement monitorin and decision ma"in &e' '% sales report( o detailed reports o summary reports o e)ception reports e)ternal output $ fre*uently ser+e as proof of business transactions &e' '% in+oice% ban" statement% payslip% phone bill( turnaround output $ e)ternal outputs that reenter the system as inputs &e' '% payment stub of a bill( typical formats! printed% screen display% e-mail% multi-media

,asic uidelines for output desi n pro+ide title% timestamps% headin s and sections% roupin s% lo ical orderin &columns and rows(% proper ali nments for printed output pro+ide appropriate labels% partitionin % intuiti+e na+i ation% hi hli htin &e' '% colors% fonts( for screen output pro+ide print options for screen output pro+ide appropriate le+el of customi-ation display rele+ant information lay out the report or screen display properly use mechanisms to contract or e)pand le+els of detail timin considerations are important pro+ide efficient and sufficient distribution of or access to system output "now how the output will be used pro+ide the necessary controls and security measures obser+e consistency in the reports enerated by a system #utput desi n process identify output re*uirements &durin re*uirements analysis( specify physical output re*uirements! consider issues related to distribution% number of copies% paper to be used% format% timin % confidentiality% etc' desi n% +alidate and test

#,.E/T-#0IENTED DESIGN &##D( concerned with de+elopin an ob1ect-oriented system model to implement re*uirements system functionality is e)pressed in terms of ob1ect ser+ices 2M3 conceptuali-ed by the Three 4mi os! .ames 0umbau h &#b1ect Modelin Techni*ue $ General Electric(% Grady ,ooch &,ooch5s method(% I+ar .acobson &##SE( an international standard that e+ol+ed from the ori inal 2M3 6'7 to 2M3 8 &+ersions 8'6 and 8'8( contains documentation behind the model elements such as written use cases basic terms o structure! actor% attribute% class% component% interface% ob1ect% pac"a e o beha+ior! acti+ity% e+ent% messa e% method% operation% state% use case o relationships! a re ation% association% composition% dependency% enerali-ation &or inheritance( o others! stereotype% multiplicity% role 2M3 dia rams used to represent a partial raphical representation of a system5s model represent three different +iews of a system model! o functional re*uirements +iew &e' '% use case dia ram( o static structural +iew &e' '% class dia ram( o dynamic beha+ior +iew &e' '% se*uence dia ram% acti+ity dia ram( cate ori-ed into! o structure dia rams! what thin s must be in the system o beha+ior dia rams! what must happen in the system interaction dia rams! emphasi-e the flow of control and data amon system components

/riticisms lan ua e bloat problems in learnin cumulati+e impedance tries to be all thin s to all people

E94M:3ES! /lass Dia rams

#b1ect Dia ram

:ac"a e Dia ram

Deployment Dia ram

WorkStation Web Browser

PDA

DataBase Server

Application Server

Access DataBase

JSP

J2ME

Servlet

2se /ase Dia ram

Se*uence Dia ram

/ommunication Dia ram

4cti+ity Dia ram