System appreciation
From Wikipedia - Reading time: 4 min
System appreciation is an activity often included in the maintenance phase of software engineering projects. Key deliverables from this phase include documentation that describes what the system does in terms of its functional features, and how it achieves those features in terms of its architecture and design. Software architecture recovery is often the first step within System appreciation.[1]
References
[edit]- ^ Patel, Sandipkumar; Yogesh Dandawate, John Kuriakose. "Architecture Recovery as first step in System Appreciation" (PDF).
Further reading
[edit]- Clements Paul; et al. (2002). "2". Documenting Software Architectures: Views and Beyond. Addison Wesley. pp. 53–101. ISBN 978-0-201-70372-6.
- Parnas, D.L. (1972). "On the Criteria for Decomposing Systems into Modules". Communications of the ACM. 15 (12): 1053–1058. doi:10.1145/361598.361623. S2CID 53856438.
- Parnas D.L. (2002). "The Secret History of Information Hiding" in Software Pioneers: Contributions to Software Engineering. Springer.
- Sangal, N.; E. Jordan; V. Sinha; D. Jackson, eds. (2005). Using Dependency Models to Manage Software Architecture. 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications. ACM.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |
Licensed under CC BY-SA 3.0 | Source: https://en.wikipedia.org/wiki/System_appreciation4 views | ↧ Download as ZWI file
EncycloReader
is supported by the 
KSF