The discussion of the SDLC is complex and is difficult to cover in this small area.
In summary:
System analysis involves deciding what you want the system (or program) to do. When I say system of course it can refer to anything from a single program to hundreds of computers executing scores of different programs. The artifacts (or products) of system analysis can be a UML description of the system via use cases diagrams, activity diagrams, and sequence diagrams (among other things). Basically it is a detailed description of what you want to design.
Design is the process of deciding how to implement what the results of the system analysis produced. The computers to use are selected, the software to use is selected (or written), and the user interfaces are decided on. The SRS's can be created either here or earlier. Many SDLC's create them at this stage.
The next stage is implementation and test. The computers and software are put in place and the system is tested to ensure that it meets the requirements in the UML..
There are volumes written on this subject. If you have any questions please feel free to contact me through Yahoo answers.
BTW - I answered this primarily because I like the answers you have given to people in the past.
2006-11-23 12:32:47
·
answer #1
·
answered by Mn 6
·
0⤊
0⤋
system analysis....
Kick Off: the contract with the client. and fully written problem.
the analysis of the problem is done. Then u create a SRS. System Requirement Specification. This id a documnet. in that u will list all the req of the clients.
Design:
The requirements found in the SRS now got thru the design form. U will design two or more design then u choose the best one. In this there r two docs involved Low Level and High Level Design....
2006-11-23 00:53:30
·
answer #2
·
answered by nataraajc 2
·
0⤊
0⤋
There's quite a bit of overlap between the two, but generally system analysis concentrates on determining impact of modification and enhancement of existing systems. System design plans out development effort to fulfill requirements, either to existing systems or new ones.
2016-03-29 06:40:35
·
answer #3
·
answered by Anonymous
·
0⤊
0⤋
System analysis and design meaning is ambiguous. When I took the class in school, it covered database design. The business problem, then the business needs, then the drawn out plans of a database, using flowcharts, erd diagrams, etc. In the working world, you can be a simple web programmer with a title like that.
2006-11-23 00:46:09
·
answer #4
·
answered by comn8u 4
·
0⤊
0⤋
The major goal of systems analysis and design is to improve organizational systems. Often this process involves developing or acquiring application software and training employees to use it.
To read more follow the source link below
2014-09-26 13:39:33
·
answer #5
·
answered by cooltut 3
·
0⤊
0⤋
I think you arew referring to the the Software Development Lifecyle (SDLC)
Intitiate - Initial concept -- ideation
Define -- Define requirements
Design -- Design to requirements
Deploy -- Deploy solution
There are variations to this and sets of deliverables out of each area including business requirements, functional specs, technical specs, training
2006-11-23 00:44:59
·
answer #6
·
answered by Phil 2
·
0⤊
0⤋
Perhaps you should take a course then...
2006-11-23 00:53:02
·
answer #7
·
answered by Anonymous
·
0⤊
0⤋