1 / 70

Design and Software Architecture

. 2. The Software Challenge. In industry, a software product is expected to be used for an extended period of time by someone who did not write the program and who is not intimately familiar with its internal designInitial specification for a software product may be incompleteSpecification is clar

rhea
Download Presentation

Design and Software Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. 1 Design and Software Architecture

    2. 2 The Software Challenge In industry, a software product is expected to be used for an extended period of time by someone who did not write the program and who is not intimately familiar with its internal design Initial specification for a software product may be incomplete Specification is clarified through extensive interaction between users of the software and the system analyst A requirements specification should be generated at the beginning of any software project Designers and users should both approve the document

    3. 3 The Software Challenge Software is ... Used for a long time Updated and maintained By people who did not write it Initial specification may be incomplete Specification clarified through extensive interaction between user(s) and system analyst(s) Requirements specification needed at the beginning of any software project Designers and users should both approve it!

    4. 4 Things Change! Users’ needs and expectations change Use reveals limitations and flaws Desire for increased convenience, functionality Desire for increased performance Environment changes Hardware, OS, software packages (“software rot”) Need to interact with clients, parent org., etc. Law and regulations change Ways of doing business Style, “cool” factor

    5. 5 The Software Life Cycle Software products go through several stages as they mature from initial concept to finished product The sequence of stages is called a life cycle It is important to design and document software in an organized way so that it can be easily understood and maintained after the initial release The person who maintains the software is not necessarily the person who writes it

    6. 6 Software Life Cycle Activities

More Related