NDLI: Using development history sticky notes to understand software architecture

Content Provider	IEEE Xplore Digital Library
Author	Hassan, A.E. Holt, R.C.
Copyright Year	2004
Description	Author affiliation: Sch. of Comput. Sci., Waterloo Univ., Ont., Canada (Hassan, A.E.; Holt, R.C.)
Abstract	Maintenance of evolving software systems has become the most frequently performed activity by software developers. A good understanding of the software system is needed to reduce the cost and length of this activity. Various approaches and tools have been proposed to assist in this process such as code browsers, slicing techniques, etc. These techniques neglect to use a central and vital piece of data available - the historical modification records stored in source control systems. These records offer a rich and detailed account of the evolution of the software system to its current state. In this paper, we present an approach which recovers valuable information from source control systems and attaches this information to the static dependency graph of a software system. We call this recovered information - source sticky notes. We show how to use these notes along with the software reflexion framework to assist in understanding the architecture of large software systems. To demonstrate the viability of our approach, we apply it to understand the architecture of NetBSD - a large open source operating system.
Sponsorship	IEEE Comput. Soc. Tech. Council on Software Eng
Starting Page	183
Ending Page	192
File Size	315217
Page Count	10
File Format	PDF
ISBN	0769521495
ISSN	10928138
DOI	10.1109/WPC.2004.1311060
Language	English
Publisher	Institute of Electrical and Electronics Engineers, Inc. (IEEE)
Publisher Date	2004-06-26
Publisher Place	Italy
Access Restriction	Subscribed
Rights Holder	Institute of Electrical and Electronics Engineers, Inc. (IEEE)
Subject Keyword	Software maintenance Costs Software architecture Computer architecture Software performance Software systems Control systems History Open source software Centralized control
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Using development history sticky notes to understand software architecture (2004).

A reverse engineering approach to support software maintenance: version control knowledge extraction

Using dependency model to support software architecture evolution

Helping various stakeholders to understand a very large component-based software

Designing a distributed software development support system using a peer-to-peer architecture

Atomic architectural component recovery for program understanding and evolution

Engineering tools to support interoperability in the development and maintenance of heterogeneous distributed real-time control systems

Why are software projects moving from centralized to decentralized version control systems?

Architecture based approach to the control software design

Using development history sticky notes to understand software architecture

Similar Documents

Using development history sticky notes to understand software architecture (2004).

A reverse engineering approach to support software maintenance: version control knowledge extraction

Using dependency model to support software architecture evolution

Helping various stakeholders to understand a very large component-based software

Designing a distributed software development support system using a peer-to-peer architecture

Atomic architectural component recovery for program understanding and evolution

Engineering tools to support interoperability in the development and maintenance of heterogeneous distributed real-time control systems

Why are software projects moving from centralized to decentralized version control systems?

Architecture based approach to the control software design

Using development history sticky notes to understand software architecture