Object Oriented Software Engineering   View all facts   Glossary   Help

subject > system > software system

software system
subject			fact

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: A distributed system is divided up into clients and servers A system is divided up into subsystems A class is divided up into methods
	is better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors
	is a subtopic of 1.9 - Difficulties And Risks In Software Engineering as a Whole
	is typically initially developed as a prototype
	is a kind of system
	must have well-described requirements if other systems or subsystems are going to use its services or communicate with it
	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

Kinds of software system :

• Cadillac system (3 facts) - A system that does more than is needed
• help system (11 facts)
• hung system (5 facts) - A system that appears to the user to not be doing anything, caused by such things as a crash, a deadlock, a livelock or an infinite loop
• large software system (8 facts)
• legacy system (3 facts) - A software system which is still undergoing evolution, but on which some or all of the original developers are no longer working
• multi-layer system (2 kinds, 6 facts)
• small software system (3 facts)

Next system: subsystem    Up: system    Previous system: safety critical system