The underlying concept of program slicing has been applied successfully by the University of Koblenz-Landau in Germany to create personalized electronic books known as âBook Slicingâ�?. A personalized electronic book is created by consolidating extracted sections (slices) of one or more original e-books based on its usersâ information needs, such as curricula planners, lecturers, students, and instructional designers (Dahn, Armbruster, U, & Schwabe, 2000; Dahn & Schwabe, 2002; Lange, 2001).
This research aims to explore the feasibility of applying this slicing concept on the System Requirements Specifications (SRS), a very important project document because all the subsequent project documents, such as design specifications, statements of work, software architecture specifications, testing and validation plans, and documentation plans, are related to it. (Sommerville & Sawyer, 1997pp 5-7)
The SRS typically is a bulky document consolidating the requirements from different stakeholders with different needs. Requirements are descriptions of a system property or attribute or constraint or how the system should behave (Sommerville & Sawyer, 1997pp 4-5) and stakeholders are people who will be affected by the system and who has a direct or indirect influence on the system requirements (Sommerville & Sawyer, 1997pp 8),. These include the core project team, subject matter experts, technical consultants, project sponsors, suppliers and customers (Robertson & Robertson, 2005). Thus, sliced SRS like sliced electronic book, at the minimum should reduce the stakeholdersâ document reading costs.
Presently, the SRS is generally distributed to all the stakeholders in full regardless of their needs.