During this course we will deal with systems, or parts of some larger systems.
System is a combination of
software and hardware that provides a solution for a bussines problem.
Process of developing that system involves a lot of people. First of all is the client, the person who has the problem to be solved. An analyst documents the client's problem and relays it to developers, programmers who build the software that solves the problem, test it and deploy it on computer hardware. This is necessary because systems today are so complex, knowledge has become so specialized that one person can't know all the facets of a bussines, understand the problem, design a solution, translate it into a program, deploy the program onto hardware, and make sure the hardware components all work together correctly.
The waterfall method for modeling of systems |
![]() |
The old way of system modeling, known as the waterfall method, specifies that analysis, design, coding and deployment follow one another. Only when one is complete can the next one begin. If an analyst hands off analysis to a designer, who hands off a design to a developer, chances are that the three team members will rarely work together and share important insights. Usually the adherents of the waterfall method give coding a big amount of project time, it takes a valuable time away from analysis and design. |
![]() |
In the new way, contemporary software engineering stress continuing interplay among the stages of development. Analysts and designers, for example, go back and forth to envolve a solid foundation for the programmers. Programmers, in turn, interact with analysts and designers to share their insights, modify designs, and strenghten their code. The advantage is that as understanding grows, the team incorporates new ideas and builds a stronger system. |