Object Oriented Software Engineering   View all facts   Glossary   Help

subject > system > software system

software system comparison table

Subject	cause by	integrate with	have	be	write as	is a subtopic of	have example	require	increase	explain	understand by	has part	use	has definition	develop by	provide	develop using	contain	have solution
Cadillac system			well-described requirements if other systems or subsystems are going to use its services or communicate with it	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors		4.8 - Reviewing Requirements						subsystem		A system that does more than is needed
help system		the application, making it context sensitive	well-described requirements if other systems or subsystems are going to use its services or communicate with it	fast to access		7.5 - Usability Principles			user's frustration	error messages		subsystem				help performing the steps of a task
hung system	deadlock livelock a single thread waiting for an unavailable resource an infinite loop a crash		well-described requirements if other systems or subsystems are going to use its services or communicate with it	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors	a simple problem statement in one or two sentences	10.5 - Defects in Timing and Co-Ordination: Deadlock, Livelocks and Critical Races	the absence of code to handle an exception					subsystem		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					which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution
large software system			requirements document for a large system	hard to understand		1.2 - What is Software Engineering?		a software architecture^3			one person	subsystem			a software development team		engineering discipline
legacy system			well-described requirements if other systems or subsystems are going to use its services or communicate with it	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors		1.6 - Software Engineering Projects						subsystem		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			well-described requirements if other systems or subsystems are going to use its services or communicate with it	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors		9.5 - Architectural Patterns						layer	multi-layer architectural pattern					layers with each layer communicating only with the layer immediately below it
small software system			well-described requirements if other systems or subsystems are going to use its services or communicate with it	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors		1.2 - What is Software Engineering?						subsystem			a programmer working alone

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