A web based library system is to be developed that provides a single interface to a number of databases of articles in different university libraries across the country. With this system, students can search for an article by either entering the title, the author’s name, or the date of publication or all. The library system first searches the local university library of the student and if the said article is not available, the system then further searches libraries of other universities. The system is also used by the library staff and they provide regular maintenance of the library system such as cataloging the various articles and performing user administration. Suppliers or publishing houses also provide new articles regularly to the system. Users can either download an article and read without printing or can make their own copy by printing depending on the copy right restrictions on the said article. User’s therefore first searches for an article and before the article can be retrieved, the user must agree on the displayed copyright law protecting the article and fee before the user can proceed to download the articled to read or print. The system keeps information on each article such as title, author and the fee. The source of these articles or where there were first published including the country of the publisher is also kept in the system. Each of these countries has their own copy right law which must be adhered to by the users i.Explain three functional requirements for this library system ii.Explain three non-functional requirements for this library system iii.Explain three system domain requirements for this library system iv.Draw a use case diagram for this library system. v.Draw a ERD diagram for this library system. vi.Draw a sequence diagram for this library system.

QUESTION 1:    CASE STUDY- SOFTWARE FOR OLA COLLEGE OF EDUCATION  

Fosu College of Education (FOSCO) is one of the colleges of education in Ghana known for its significant drives for quality education in Ghana. The college have a software that keep records of all academic records of the college. In recent times, management descried to outsource and develop a state-of-the-art software which will keep all the relevant records of the college’s research activities. As a consultant, the following information about a college database was outlined to you during the project initiation state and requirement stage:     Professors have an SSN, a name, an age, a rank, and a research specialty. Projects have a project number, a sponsor name (e.g., GETFUND), a starting date, an ending date, and a budget. Graduate students have an SSN, a name, an age, and a degree program (e.g., M.S. or Ph.D.). Each project is managed by one professor (known as the project’s principal investigator). Each project is worked on by one or more professors (known as the project’s co-investigators). Professors can manage and/or work on multiple projects. Each project is worked on by one or more graduate students (known as the project’s research assistants). When undergraduate students work on a project, a professor must supervise their work on the project. Students c work on multiple projects; in which case they will have a (potentially different) supervisor for each one. Departments have a department number, a department name, and a main office. Departments have a professor (known as the chairman) who runs the depa rtment. Professors work in one or more departments, and for each department that they work in, a time percentage is associated with their job. Graduate students have one major department in which they are working on their degree. Each graduate student has another, more senior graduate student (known as a student advisor) who advises him or her on what courses to take.  Answer the following questions; a. As a software engineer, develop an appropriate requirement analysis of the case. You may note any unspecified requirements from the scenario, and make appropriate assumptions to make the specification complete. b. D raw the following diagrams of the system i. : Flowchart  ii. to depict the scenario towards the development The Context Level Diagram iii. iv. Entity Relationship Diagram  Data Flow Diagram for FOSCO specifying the key attributes of each entity type, and the structural constraints on each relationsh v. c. Use case diagram for the case 

iv.Draw a use case diagram for this library system.
v.Draw a ERD diagram for this library system.
vi.Draw a sequence diagram for this library system.