Please enable JavaScript.
Coggle requires JavaScript to display documents.
SAD ch1 (introduction to analysis and design) (chapter 1 introduction to…
SAD ch1 (introduction to analysis and design)
chapter 1 introduction to analysis and design
why need SAD?
create system is not intuitive
avoid late/over budget/fewer features than planned
failures occur often
key person in system analyst
add value
understand the business
rewarding and challanging
requires spesific skill set
system development life cycle (SDLC)
4 phase(each contain series of steps)
analysis
who/what should/where/when
I) develop an analysis strategy
model the current system
formulate the new system
II) gather the requirement
develop system consept
create model represent:
business data
business process
III) develop a system proposal
implementation
I) construct the system
build it (code it)
test it
II) install system
train user
III) support the system (maintenance)
design
how
I) develop a design strategy
II) design architecture and interface
III) develop database and file specification
IV) develop the program design to specify
what program to write
what each program do
planning
why/what does/how
I) project initiation
develop/receive system request
conduct feasibility analysis
technical (manpower, do-able , existed ?)
economical (cost efficient , should build ,worth ?)
organizational (they gonna use ?)
II) project management
develop work plan
staff for project
monitor and control project
executed sequentially
each phase is documented
methodologies
to formalized approach to implement SDLC
catagories
process oriented
data centered
object-oriented
structured development
waterfall development
parallel development
rapid application development
phased
prototyping
agile development
eXtreme programming
SCRUM
the system analysist
SA skills
agents of change
motivte and train others
identified ways to improve organization
skill needed
technical: understand the techonoogy
business:know the business processes
analytical: able to solve problems
communications:technical & non-technical audieences
interpersonal: leadership & management
ethics:deal fairly & protect confidential information
SA roles
business analyst
analyzing key business aspect of system
identified how that system will provide business value
design new business process policies
system analyst
identified how tech can improve business process
design new business process
design information system
ensure system conform to information system standarts
infrastructure analyst
ensuring system conforms to insfrastructure standarts
identified infrastructure changes needed to support system
change management analyst
develop and execute change management plan
develop and execute user training
project manager
manage the team
develop and monitor the project plan
assigning resources
serve as primary point of contact for project
object -oriented
systems analysis & design
attempts to balance data and process
utilizes the unified modeling language(uml) and unified process
characterristic
use-case driven
architecture centric
iterative and incremental
chapter 2 Project management