1. CMPT 370 Course Project Library Information System Analysis and Design

2. Your Project TA Where: CSIL MTF Lab When : Monday 12:30-1:30 Wednesday 15:00-17:00 Friday 11:30-12:30 Or By appointment Email: htw@sfu.cahtw@sfu.ca

3. The Menu Introduction Stake-Holders Analysis Component Design Component Question and Answer

4. Introduction Library is a repository of Information The information comes in a wide variety of formats The library system is complex A perfect system does not exist Determine the most crucial components The project is limited by the time available

5. The Information Pot Paper based information: books, journals, magazine, newspaper, and maps Multimedia based information: CDs, VHS, DVDs, LPs, Internet Connected Computers A connected set of repositories

6. The Stake-Holders Users Librarians Library Administrators Others ?

7. The Users Diverse group Varying  Expectations  Way of thinking  Experience  Familiarity with library systems  Circumstances The library is build for the people that uses them, and so must the system we’re building.

8. The Librarians Knowledgeable professional Sub-Pools handled by one librarian Helpers for users Manages the information pool. Knows the intricate details of the library

9. Library Administrator Decision maker Sometimes Librarians take on this role Make book purchases Can be the central authority of all branches High level view

10. What are we doing? The ultimate goal  Satisfy all the stake-holders to within some reasonable limits (Making tradeoffs).  Ensure the software is maintainable, upgradeable, and extensible Find out what is necessary (Analysis) Turn it into something you can implement (Design)

11. The Menu Introduction Stake-Holders Analysis Component Design Component Question and Answer

12. Analysis A.K.A Requirements gathering Interview all the stake holders Observe the current process Put the observation into a model

13. Analysis (What To Do) Model the domain (as-is:to-be) Domain models should be simple but… Document the functional requirement using use-case and use-case diagrams Document the vocabulary used within the domain Domain model will help you limit the scope of the project

14. Analysis Complete capture of the domain is essential Look for Implicit requirements A thoughtful model is required CRC method is recommended

15. The Menu Introduction Stake-Holders Analysis Component Design Component Question and Answer

16. Design (Putting Your Analysis to Work) Translating the domain model into models that developers can understand. Tools of the trade:  Use-Cases( Which you should have done)  Class Diagrams  State Diagrams  Interaction Diagrams  Activity Diagrams,  Component Diagrams  Architecture Diagrams Make use of any of the tools needed

17. Design One step before implementation Detailed design is necessary for a completely new system However re-use of pre-existing implementation can possible reduce the design granularity The design documents must clearly reflect what the implementation will look like.

18. Design Remember the goal of the system Time is the biggest issue.

19. The Menu Introduction Stake-Holders Analysis Component Design Component Question and Answer