![]() |
subject > system > software system > large software system |
![]() ![]() | ||||
large software system | ||||
subject | fact |
large software system | cannot be understood by one person | ![]() |
has requirements document for a large system | ![]() | |
is hard to understand | ![]() | |
is a subtopic of 1.2 - What is Software Engineering? | ![]() | |
is a kind of software system | ![]() | |
must be developed by a software development team | ![]() | |
must be developed using engineering discipline | ![]() | |
requires a software architecture^3 | ![]() | |
software system | becomes complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features | ![]() |
can automate business process | ![]() | |
can be divided in many ways:
| ![]() | |
is typically initially developed as a prototype | ![]() | |
should be designed for flexibility right from the start | ![]() | |
undergoes evolution over its life-span | ![]() | |
system | can have specification which is then implemented by a collection of components | ![]() |
exists even if its components change over the course of time, or are replaced by equivalent components | ![]() | |
has scope | ![]() | |
has part component | ![]() | |
has part hardware | ![]() | |
has part module | ![]() | |
has part software | ![]() | |
has part subsystem | ![]() | |
is divided up into subsystems | ![]() |
Next software system: legacy system Up: software system Previous software system: hung system