COIT20248: Information Systems Analysis and Design Term 2, 2015 Assignment 2. Lecturer: Dr. Meena Jha Tutor: Aries Tao

Transcription

1 COIT20248: Information Systems Analysis and Design Term 2, 2015 Assignment 2 Lecturer: Dr. Meena Jha Tutor: Aries Tao Prepared by: AXXXX XXXX: S0XXXXXX AXXXX MXXXXX: BisXXXXX BaXXXX: S0XXXXX S02XXXX SXXXXX MXXXXX: S02XXXX

2 Contents 1 Introduction Broadway Bookshop Company description Objective and Methodology Report Outline Critical Use case diagram Context Diagram Level-0 DFD Diagram ERD Diagram CRUD Diagram Data elements Website Design and Architecture Objectives Aesthetic: Visual Design The Key elements User Interface Conclusion References Appendix A. Individual group members contribution... 24

3 1 Introduction 1.1 Broadway Bookshop Company description The Broadway Book Shop is a book selling store. It's a medium-sized business with around 50 employees. Its customers are mainly Universities, big organisations and individuals who are interested in buying books. At the moment The Broadway Book Shop offers 10 major genres of books, such as Science fiction, Drama, Action and Adventure, Romance and others. Broadway Book Shops main business is to acquire books from different publishers and sell and ship books to customers. Its business processes are manual. Carrie Douglass has hired AWSIG Company, as consultants to carry out analysis and develop the specifications for an automated Book information system. The desired Information system should tie together all the key elements of Book shop transactions and solve problems with current system. 1.2 Objective and Methodology The objective of this report is to provide modelling diagrams and the website design that were developed for the Broadway Bookshop Company by Australia Wide System Integration Group (AWSIG) Company. Initial planning and analysis of the Broadway Bookshop Project was done in Assignment 1. This included the chosen approach for systems development, list of primary functional and non-functional requirements, project cost benefit analysis, project planned schedule with Gantt chart, system information requirement investigation techniques. Information contained in this report has been primarily sourced from academic textbooks. 1.3 Report Outline The report will first discuss critical use cases of the case study. Second, it will represent context and level-0 DFD diagrams. Third, it will explain data modelling approach through the use of ERD, CRUD diagrams and list of necessary data elements. The report will conclude with the website design prototype and its architecture. 1

4 2 Critical Use case diagram According to Kendall & Kendall (2011), the use case scenario has three key areas. They are as follows: 1. Use case identifiers and initiators 2. Steps Performed 3. Conditions, assumptions and questions. Use Case Name Broadway Book shop Area: Book Business Planning Actors: Customer, Employee, Shipper and Supplier Description: Allow customer to register online for purchasing books using a secure website Triggering Event: Customers use Broadway Book shop Information system website signup, enters username and password, and logon to the system Trigger Type: External Steps Performed Information for the steps 1. Customer Login using secure Valid username and password Web server 2. Registration information is Registration Web form validated through valid address (for reference: Gmail, Hotmail, Yahoo Account address)on the web server 3. Add Registered customer Confirmation Web Page 4. Customer record is updated Customer Record 5. Successful Registration Registration Record Confirmation Code Confirmation Web page 6. Customer placing the order Checkout Web Page 7. Credit card charged for Secure Credit Card Web Page confirmation of the order with shipping charges included 8. Successful Placing the Order Confirmation of the Web Page, payment statement passed to the customer address and report to the employee. Preconditions: Customer has already registered and created an account Postconditions: Customer has successfully placed the order Requirements Met: Allow customer to place the book order using secure website. Assumptions: Customer has valid username and password Outstanding Issues: Handling rejected Credit card Risk: Medium Table 1 Broadway Book shop use case scenario 2

5 Based upon the condition the use case can be described in many ways. The use case shown below in Figure 1 describes the behaviour of the Broadway Book Shop Information System and assists for the interaction with the team member for its development. In this system there are 4 total actors. The customer is the primary actor of the system which initiates an interaction with the system to achieve a goal of the system. Figure 1 Use case diagram From the above observation, the critical use case is Place Order as it depends on the inventory data of the system. The customer can confirm the order only when there is availability of the stock in our system. The action called Place Order is the main action of our system since without performing this action; no further processes are worth of accomplishing. 3

6 3 Context Diagram Context diagram is highest level of data flow diagram that have only one process depicting the entire system and the process is denoted as zero(kendall & Kendall 2011). The diagram only shows the major external entities and its data flow to and from them. Context diagram is equivalent as an architect developing the blueprint before designing the house. Similarly, before designing or developing the system context level diagram is made. It is the prototype made before designing the system. The following is the context level diagram of the Broadway Bookshop. Figure 2 Broadway Book Shop Context Level Diagram Figure 2 represents the context diagram. The Broadway Book shop Information System has five entities (Customer, Employee/manager, Shipper, Supplier and Payment processor) that are placed around the fundamental system. The Customer entity supplies the data through the customer order and receives the data through the receipt of the order that they make. The Payment Processor entity receives the data through Payment info and supplies the confirmation of payment data to the system. Likewise, the employee/manager entity supplies the data of list of books and receives the reports data from the system. The supplier entity receives the book orders list from the system and supplies the supplied book bills in return. Correspondingly, the shipper entity receives the shipping request data and supplies the shipping details information. 4

7 4 Level-0 DFD Diagram Level-0 DFD diagram (see Figure 3) shows the information system s main processes, data stores and data flows and is the expanded version of the context diagram which represents the entire information system (Shelly & Rosenblatt 2012). Figure 3 DFD level 0 Diagram of Broadway Bookshop Based on the context level Diagram, DFD level 0 is drawn. Figure 3 shows the DFD Level 0 diagram of Broadway Bookshop. There are five entities. They are Customer, Employee/Manager, Supplier, Payment Processor and Shipper. As shown in the figure, there are three stores. They are Inventory File, Sold Items and Book Delivery File. There are six processes. The six processes are Process Customer Book Order, Update Inventory File, Process Payment, Sell Book, Deliver Book and Generate Report. The Data Flow are as follows: 1. Customer Order 2. Inventory Data 3. List of Books 4. Payment Confirmation Details 5. Sold Item data 6. Shipment Details 7. Shipping Requests 8. Book Delivery File 9. Formatted Inventory Data 10. Book Orders 11. Reports 5

8 12. Daily Sold Book Amounts 13. Supplier Bills 14. Payment Info 15. Confirmation of Payment 16. Book Delivery Information 17. Receipts 18. Reports 19. Daily Book Delivery 5 ERD Diagram 6

9 An entity relationship diagram is a model that displays the logical connections and interaction between the system entities. An ER diagram gives an overall view of the system and a design for creating the physical data structures (Shelly & Rosenblatt 2012). There are two terms used in ER diagram namely primary key and foreign key. Primary key is the unique attributes of the whole relationship of the system whose value must be different to other value of the attributes. Foreign key is an attribute that is primary attribute in one relation and become non primary attribute in another relation. There are three types of relationship between the two entities. They are as follows: 1. One to one relationship 2. One to many relationship 3. Many to many relationship 4. Many to one relationship Figure 4 shows the ER diagram of Broadway Bookshop. The entities in our system are customer, order, inventory, Invoices, Supplier and Payments, Shipper, Sales item, and Employee. The attributes are defined below the entities. The PK represent Primary key and FK represents foreign Key. The cardinality is shown between the entities. Thus, designing the ER diagram of the system gives the base of the database and visualizing the how the data will be stored in the system. 7

10 Figure 4 ERD diagram of Broadway Bookshop 8

11 6 CRUD Diagram CRUD diagram also known as CRUD matrix is a physical data flow diagram that explains four different actions that are performed in the system. The four actions are Create, Read, Update and Delete. Physical or CRUD diagram may cover many items which are not found in logical data flow diagram. Data entry and verifying process are also listed on the CRUD matrix. It also has data stores and transaction files. Following is the CRUD matrix table based on the logical data flow diagram. Table 2 CRUD diagram The table shows the CRUD diagram of Broadway Bookshop. It has for entities and eight process. The row contains entities like Customer, Employee/Manager, Supplier and Shipper. Employee/ Manager can perform almost all the processes and thus have the administrator privileges. The privileges of the based upon the entity. 7 Data elements 9

12 The data elements with data entities are defined below: 1. Customer No. Column Name Data Type Size Constraints 1 Customer ID Number 20 Primary Key 2 Name text 20 3 Mobile Number 10 4 Address Text Order No. Column Name Data Type Size Constraints 1 Order ID Number 20 Primary Key 2 Customer ID Number 20 Foreign Key 3 Book ID Number 20 Foreign Key 4 Quantity Number 5 5 Order Date Number Inventory No. Column Name Data Type Size Constraints 1 Book ID Number 20 Primary Key 2 Name Text 20 3 Author Text 20 4 Description Text Employee No. Column Name Data Type Size Constraints 1 Employee ID Number 20 Primary Key 2 Name Text 20 3 Phone Number Supplier No. Column Name Data Type Size Constraints 1 Supplier ID Number 20 Primary Key 2 Name Text 20 3 Company Name Text 20 4 Supplied Date Number Shipper No. Column Name Data Type Size Constraints 10

13 1 Shipper ID Number 20 Primary Key 2 Customer ID Number 20 Foreign Key 3 Name Text 30 4 Shipment Date Number Sales Item No. Column Name Data Type Size Constraints 1 Sales ID Number 20 Primary Key 2 Transaction ID Number 20 Foreign Key 3 Author Text 20 4 Description Text Payments No. Column Name Data Type Size Constraints 1 Transaction ID Number 20 Primary Key 2 Customer ID Number 20 Foreign Key 3 Transaction Date Number Invoices No. Column Name Data Type Size Constraints 1 Invoice ID Number 20 Primary Key 2 Transaction ID Number 20 Foreign Key 3 Price Number 10 11

14 8 Website Design and Architecture The competitive stage of business initiates towards development of the e-commerce software where the entrepreneur facilitates their users and hence the users are fascinated to the services of the organization. Thus, analysing the needs of the development and for the eradication of the problem faced due to old system, Broadway Book shop aims towards the development of the software. Before actual development of the system, Australia Wide System Integration Group (AWSIG) plans to design the website prototype. The prototype of the website is built using tools like Notepad++, HTML, CSS and JavaScript. Generally, the prototype of the website is designed to understand the requirements of the system without freezing the requirements before actual coding is done. 8.1 Objectives The objectives of designing the prototype of the system are as follows: It gives the actual feel of the system The prototype provides the quicker user feedback and the changes are identified. It gives clear concept of the website interface layout. Identification of missing functionality. 8.2 Aesthetic: Visual Design This system aims to satisfy the customer and targeted to gain maximum profit in near future. The users now use mobile more than any other devices. The system is designed on the mobile platform. Therefore, the system is designed to provide interface usability and allow users to browse in effective and efficient ways. 8.3 The Key elements Life started getting good when I started making money, says Balthazar Getty. Therefore, for better living, the life of the people seems busy. Visualizing the need of time, the website is so designed that it saves the time of everyone. The key element of the website is the search navigation showing in every page where the customer visits. The customer can easily search the books when they are willing to buy and saves their valuable time. Additional to this, it provides 24*365 hour services to the customer. Therefore, the customer can spend their time on buying the book whenever they like. 12

15 8.4 User Interface The user interface of the Broadway Book shop is represented below: Figure 5 Login/Signup page 13

16 Figure 6 Home page 14

17 Figure 7 Book page (filter according to Genre) 15

18 Figure 8 Book details Page 16

19 Figure 9 Cart Page 17

20 Figure 10 Checkout Page 18

21 Figure 11 Wish list page 19

22 Figure 12 Contact Us Page 20

23 Figure 13 Account page Assumptions: Internet service is available Customers have the latest browser installed in their devices as some of the features may not be functional in old browsers. 21

24 9 Conclusion The report discussed the modelling diagrams and the website design for the Broadway Book shop. Firstly, use case diagram was shown to describe the high level behaviour of the Broadway Book shop Information System. Next, the Context level Diagram and level-0 DFD diagram were developed to show the main entities, business processes and data flows. Thirdly, the Entity Relationship Diagram was represented as a model to display a logical connection between system entities. Fourthly, data entry and verify process were listed on the CRUD matrix. Finally, the website was designed and its architecture was shown. The website is user-friendly and the customer will save time as it is possible to shop online. The developed website design and its architecture will give a competitive advantage for the Broadway Bookshop and the feedback from the customer can be taken for the future improvement of the desired information system. 22

25 10 References Kendall, K & Kendall, J 2011, System analysis and design, 8 th edition, Pearson Education, New Jersey. Shelly, G, Cashman, T & Rosenblatt, H 2012,System analysis and design, 9 th edition, Cengage Learning, Boston. Valacich, J, George, J & Hoffer, J 2012, Essentials of systems analysis and design, 5 th edition, Pearson Education, Prentice Hall, Upper Saddle River, N.J. 23

26 Appendix A. Individual group members contribution Details of individual group members contribution towards the development of the project Task Assessed XXXXX (S0XXXXX) XXXXX (S0XXXXX) Members XXXXX (S0XXXXX) XXXXX (S0XXXXX) 1. Case study Analysis 2. Data Analysis and Gathering Requirements 3. Use Case Diagram 4. Context Level Diagram 5. DFD Level 0 Diagram 6. ERD Diagram 7. CRUD Diagram 8. Website prototype 9. Report Writing 10. Analysing the benefits and limitation of tools used in building prototype 11. Presentation Slide 24