SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Design and Software Architecture

rhea avatar
rhea
70 diapositives · 948 Views · Jun 29, 2012

. 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

#systems design #software architecture #requirements traceability #phase #spim #cad #computer architecture #hierarchical visitor pattern
Design and Software Architecture - slide 1
01 / 70Design and Software Architecture
1 / 17

Télécharger la présentation

Design and Software Architecture
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

    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