1. CSE 784 Software Studio Syracuse University
Avinash T. Suresh
Rahul Chandrasekaran
Francisco Zurita
Simin Zhao
CSE 784 Software Studio
Syracuse University

2. System Context and Modular Decomposition Processes and Data Flows
Introduction
System Context and Modular Decomposition
Processes and Data Flows
Functional Requirements
Prototypes
What’s new this time?
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

3. Some of the salient features are:
The Repository maintains a persistent and versioned set of components and items.
The Repository is designed to help manage code and documentation in a large software development project.
Some of the salient features are:
Source and documentation check-in, check-out and versioning.
Reporting and Logging information.
Garbage collection and Authentication.
Search and intellisence.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

4. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

5. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

6. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

7. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

8. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

9. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

10. The Repository shall provide means of storing all products developed by the RSA system, with dependency information entered at check-in .
(a) Products shall include source code, test code and documentation files.
(b) Dependency information shall either be provided during the check-in or shall be allocated/modified at a later state.
(c) In case the dependency is not provided at startup it shall be added to the shared pool of items in the system.
Check-in shall be allowed only if item is presented with all files to which this check-in refers, if they are not already in repository.
Check-in shall fail if any of the items referenced by current item is open.
(a) User shall not be allowed to select open items as references for items that are checked-in.
Addition/Modification of new parts to open check-in shall result in overwriting previous files.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

11. Shall support of cancellation of check-out of item.
(a) A new version check-in shall not be allowed if a previous check-out has been cancelled.
(b) A cancellation of check-out shall discard open check-ins of the item with a warning.
Shall not allow check out of non checked-in item.
(a) Shall not allow selection for checkout of items not existing items in the repository(not checked-in previously).
Shall not allow open items to be checked out.
(a) Open items can only be extracted and not checked out.
The Repository shall provide a mechanism to close an open version. Once a version is closed, it is immutable, and may be referenced by any other component.
(a) An open check-in can be closed in which case the open state ceases to exist thereafter.
Intellisence for displaying existing module names when the user performs a new check-in.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

12. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

13. Every stored product shall be assigned a version number by the Repository, in one of two states, open or closed.
(a) Any version of an item can exist either as open check-in or closed check-in, not both.
(b) A closed check-in cannot be set as open again without checking out (and checking in as a new version).
All files supplied for check-in process shall be given a new version number.
(a) A new version number is assigned only if the latest version of the stored product has been previously checked out.
(b) A new version number is assigned both in the case of an open or a closed checkin.
The Repository shall support the modification or addition of new parts to an open check-in without re-versioning.
Shall not allow checkout of old versions
(a) Only the latest version shall be allowed for checkout.
(b) Older versions can only be extracted and not checked-out.
Shall provide naming service for package, class and document naming.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

14. Shall provide means to add/delete/modify RI for each module.
(a) Shall provide administrator services to add/delete/modify the RI of the module.
(b) The RI of a module shall be allowed to be added, deleted or modified by the author of the module or the administrator.
(c) Shall allow any RI to check-in a new document but shall allow RI to be changed later.
Shall allow only RI to change the status from open to close and shall allow only one RI per module.
(a) Shall allow only one RI at one time, to be added per module.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

15. Shall not allow deletion of item which is referenced by other items.
(a) Shall provide a garbage collection scheme which allows deletion only of those items which are not already referenced by other items.
Garbage Collection
Reference counting for each item
Option for automatic deletion of items whose reference count turns zero upon deletion of the referencing component.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

16. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

17. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

18. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

19. Versioning (information and computation)
Handling various states – checked-in (open and closed), checked-out, etc
Versioning (information and computation)
Reference counting for garbage collection
Logging information for change logger
Managing items and components
Maintaining dependency information.
Authentication
And lots more…..
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

20. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

21. [B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

22. State Action-Mapper example code Message builder (Dr. Fawcett)
File Handler
State Action-Mapper example code
Message builder (Dr. Fawcett)
XML processor
Manifest builder and parser prototype
GUI prototype
Design structure prototype
Shared database component dictionary and message format.
[B-Spec: Repository and Data Management System]
[10/08/2006] Version 1.0

23. Thank You!