Object Oriented Analysis and Design - Report Example

Object Oriented Analysis and Design The project I selected is about:- Book Store system Contents Contents 2 System Background 3 Project Lifecycle 4 Fact Finding Techniques 5 Requirements Definition 7 Functional Analysis - Use Case Diagrams 8 Functional Analysis - Use Case Descriptions 11 Functional Analysis - Activity Diagrams 12 14 Fig 8: Activity Diagram 2 14 Structural Modeling – Class & Object Diagrams 14 Behavioral Models 16 18 Data Base Design 19 Human Interaction Design – User Interface Storyboard 19 Action Plan 21 References 22 Appendix 23 System Background Green field University Green field University is the business to study in this project. It is one of the major universities in the region. It was established in 1984 by the Green field University Act of Parliament. It is located in Southern town which is a rapidly growing industrial town. Green field University was established as an institution of Science and Technology with relatively small component of arts based programmes. The first group of 83 students was admitted in 1984, Since then, the University has experienced phenomenal growth from the initial one Faculty in 1984 to 15 Faculties in 2013 spread across the six campuses of Green field University. The developed information system will serve a population of over 22,000 customers. These include student, lecturers and surrounding community. PROBLEM DESCRIPTION Green field University faces a lot of problems owing to the current information system employed in the books recording and tracking. There are so many books to be recorded, tracked and managed. The university currently uses an off the shelve software. This software is too general and cannot meet the specific needs of the users and management. The current system in use do not provide for online access by other campus users. This makes it difficult for Book Store management to serve all the campuses effectively. The system is indeed not economical in terms of cost, speed and reliability. PROPOSED SOLUTION There is need therefore for a system that will allow for online access. This calls for an online Book Store information system which will allow for processing of orders from various locations by authorized individuals and print out reports from the different campuses. Project Lifecycle This project adopts the Extreme Programming Methodology (XP). XP has four core values; these include communication, simplicity, feedback, and courage. The developers adopt this approach to create any system. The approach allows for rapid feedback to the end users on a continuous basis. It also enables the developers make incremental changes to grow the system and they must not only accept change, they must embrace change. The developers here work as a team and help each other build their skills. The approach therefore create successful systems by continuous testing, simple coding performed by pairs of developers, and close interactions with end users to build systems very quickly. The information system development will also adopt the object oriented approach where Unified Modeling Language (UML) is used. This object oriented approach has been adopted because of its characteristic that reflects the system as objects which is more understandable. UML is one of the languages that provide a comprehensive notation for communicating the systems requirements, architecture, implementation and deployment. Fig 1: Extreme Programing Methodology Fact Finding Techniques In this project, Interviewing was adopted as a tool for facts finding. This is a direct face-to-face conversation between the developer and users. The developer obtains answers to questions he asks the interviewee. He gets the interviewee’s suggestions and recommendations that will assist during the design of the proposed system. Interviews were adopted because of the following:- The analyst can frame questions differently to individuals depending on their level of understanding. The analyst can observe non-verbal communication from the respondents or interviewees The response rate tends to be high Provides immediate response The analyst can get detailed facts from each respondent Interview process My interview will be conducted with the ICT staff in green field university. First of all the director will be interviewed followed by staff members and finally users. The purpose will be to collect facts on the current system, determine option for a proposed system and understand the business background. I will ensure to build rapport with the interviewee, so that he trusts me and is willing to give the whole truth, not just give the answers that he or she thinks was wanted. Everything that the interviewee will say shall be noted down even if it did not appear immediately relevant. Facts will then be separated from opinions and finally the interviewee will be allowed to ask questions towards the close of the interview. Post interview follow up will finally be done after completion of the report. Language barrier, time and weather condition may offer a challenge but all that will be factored in during planning. Fig 2: Interview schedule Requirements Definition According to the facts finding conducted the following findings were noted:- There is a Book Store information system in place. The nature of system in existence is not a typical system that users are contented with. The system is not accessible online and therefore users in different campuses have difficulty accessing Book Store services. From the observation during the interview, the graphical user interface is not user friendly. There is no provision in the system to generate reports of placed orders. The Book Store items have no barcodes to assist in items searching and tracking. The system do not performed all the required processes and procedures as required by users. The users also found that most of the Book Store management procedures and processes of the current system were complex and procedural. An interview with the head of the ICT section of the university indicated that the current system was acquired as an off-the-shelve software and therefore it is not tailor made to suit the clients and users needs. Functional Analysis - Use Case Diagrams Fig 3: use case 1 Fig 4: use case 2; Actor – customer Fig 5: use case 3 Fig 6: use case 4 Functional Analysis - Use Case Descriptions The book store system has a provision for customer registration, it has a catalog which a records of all the books in store. Once a customer registers and log in, the book store system is able to retrieves the Orders that Customers placed and display in the Orders Tracking report. Every order entry has a unique ID, date, status, recipient, and the Shipping mode. When the Customer selects on a link; the system retrieves the relevant contents of the Order, and display the record in report format. If the customer has not placed any order, then the system displays a message to that effect on the order tracking report. Functional Analysis - Activity Diagrams Fig 7: Activity Diagram 1 Fig 8: Activity Diagram 2 Structural Modeling – Class & Object Diagrams Class Diagrams Fig 9: Class Diagram 1 Object diagram Fig 10: Object diagram Behavioral Models Sequence diagrams Fig 11: Sequence diagram 1 Fig 12: Sequence diagram 2 Data Base Design Table Name: Customer table Field Name Data Type Constraint (e.g. P.K. OR F.K) Sample acceptable attribute value Name Varchar2(20) P.K Kenneth Age Date F.K 20/07/1982 Area of interest Varchar2(20) P.K Chemistry Table 1: Customer table Table Name: Order table Field Name Data Type Constraint (e.g. P.K. OR F.K) Sample acceptable attribute value date Date F.K 20/07/1982 Total_amount Number(6,2) P.K 12,000.00 Table 2: Order table Table Name: Books Table Field Name Data Type Constraint (e.g. P.K. OR F.K) Sample acceptable attribute value Book Number Varchar2(10) P.K A12456789X Author Varchar2(20) P.K KEN BIN Price Number(6,2) F.K 12,000.00 Table 3: Books Table Table Name: credit Card table Field Name Data Type Constraint (e.g. P.K. OR F.K) Sample acceptable attribute value Card No Varchar2(15) P.K 01234566789 Balance Date F.K 20/07/1982 Table 4: Credit Card table Human Interaction Design – User Interface Storyboard System log in User Interface Storyboard 1: System log in Book search by Book Number User Interface Storyboard 2: Book search by Book Number Navigation Form User Interface Storyboard 3: Navigation Form Control Use Case Description Screen No. Reason for Use 1 Use case 4 1 Log in 2 Use case 6 2 Searching 3 Use case 3 3 navigation Action Plan References Kendall, Kenneth E. and Kendall, Julie E. (1992) Systems Analysis and Design, New Jersey; Prentice Hall.pp325-385. Kendall, E.K. and Kendall, J.K. (2011) “Systems Analysis and Design”, 8th (Global) Edition, Pearson Education. Martin Fowler and Kendall Scott. (2005) UML Distilled, A Brief Guide to the Standard Object Modeling Language. New Jersey; Prentice Hall. Wielder holds, Gio (1993) Database design 2nd Ed. New York: McGraw-Hill Appendix Read More