Show simple item record

dc.contributor.authorBritton, C.
dc.date.accessioned2010-07-16T10:54:06Z
dc.date.available2010-07-16T10:54:06Z
dc.date.issued1992
dc.identifier.citationBritton , C 1992 , Do we still need the system life cycle? UH Computer Science Technical Report , vol. 135 , University of Hertfordshire .
dc.identifier.otherPURE: 99508
dc.identifier.otherPURE UUID: 06261fb8-bdb4-4150-81f0-40e88c58a701
dc.identifier.otherdspace: 2299/4660
dc.identifier.urihttp://hdl.handle.net/2299/4660
dc.description.abstractSince the dawn of software systems the development process has been dominated by the traditional system life cycle. This is a route map, onto which a software project fits more or less comfortably, and which prescribes the stages through which such a project must pass on its way from being merely an idea in the customer's mind to implementation and delivery. It is true that, in recent years, techniques such as prototyping and the use of formal notations have been developed which seem to encourage a move away from a rigid life cycle approach; yet software projects based on these techniques seem to be significant more for the fact that they do not follow a life cycle pattern rather than that they do introduce a new development framework.en
dc.language.isoeng
dc.publisherUniversity of Hertfordshire
dc.relation.ispartofseriesUH Computer Science Technical Report
dc.rightsOpen
dc.titleDo we still need the system life cycle?en
dc.contributor.institutionSchool of Computer Science
dc.relation.schoolSchool of Computer Science
dcterms.dateAccepted1992
rioxxterms.typeOther
herts.preservation.rarelyaccessedtrue
herts.rights.accesstypeOpen


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record