Domain Modeling and Requirements Specification Using Uml - Report Example

Letter of transmittal This report has been prepared and written by from scratch. This report is intended to help in designing a system that will be used by Bill Wiley to manage the business of package picking. The audience that is intended to benefit from this report is the stakeholders in business. This report is particularly intended to be used by Bill, the owner of the business. It was written so that it captures the main issues that need to be considered when developing the system. It will be helpful for the system developers. Before a system is developed, there is need to have a clear analysis of the system which is being developed so that the main issues that are on the ground are captured. It is therefore intended for system analysts and software developers as so that they will get what the new system is to capture. The main outcome of the report is that an extensive web-based system should be designed that will capture all the requirements. It found out that interactivity of the system should be taken into consideration as the system will be accessed from many places. For this reason, there should be a good update system that will enable changes to be captured effectively. Shift and Swift Courier Automated System Executive summary With the advent of information systems, the importance of system analysis cannot be understated. This process in an important one as it helps to get the gist of the system that is being developed. The new system to be developed needs to be up to date and solves the problem that has been stated. It also helps eradicate bugs and errors that come up. This paper will look at the design issues and the blue-print of the system that will be developed for Shift and Swift System. The paper will come up with design issues that need to be considered when designing the system. Table of contents Letter of transmittal 1 Executive summary 3 Table of contents 4 Introduction 5 Case background 5 Request for information System Services 6 BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE 6 BRIEF STATEMENT OF EXPECTED SOLUTION 7 PIECES framework 7 Problem Analysis 7 Context Diagram 9 Tentative List of Requirements 9 Use-Case Glossary 11 Initial model diagram 12 Refined UML 12 Use-Case Model Diagram 12 Use-Case Narrative 14 Conclusion 16 References 17 Introduction System design and analysis requires a lot of issues that needs to be looked into when undertaking the design of any new system. There is a need to ensure that the system meets the requirements of the users who will use the system. In system analysis, the UML use cases and entity relationship management are among the things that need to be looked into. This paper will look at the use case and other design issues that need to be considered in the new proposed system. Case background Shift and Swift Courier is a company that deals with shipment of items from source to destination. It is based in Melbourne and has Bill Wiley as the CEO and director. The system has been operating manually without any automation. There has been therefore a need to automate processes and this is what the paper will work on. Request for information System Services SUBMITTED BY (key user contact) EXECUTIVE SPONSOR (funding authority) Name Name Name Bill Wiley Title Analyst/ Programmer Title Owner Office Office Phone ext. 432 Phone ext. 233 TYPE OF SERVICE REQUESTED:  Information Strategy Planning  Existing Application Enhancement  Business Process Analysis and Redesign  Existing Application Maintenance (problem fix)  New Application Development  Not Sure  Other (please specify ________________________________________________________ BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE For a long time, the handling of the shipping processes of Shift and Swift enterprise has been manual. With the extension of the business and increase in the number of employees many significant problems were faced in the shop .The following is a list of Examples 1. Billing: the bill was filled by the employees manually and there were many mistakes made e.g. (The amount of product requested was mistaken, the product name also not recorded on the invoice). 2. Miscommunication among the branches for a customer order, for example a customer ships an item from a location and it loses track. Not only about stock location but products cost is a same or not and quantity about each product. That’s the reason of miscommunication among the branches. As a result of problems mentioned above, it may make cause delay in business procedures and waste of time for both customer and staff. It also requires physical efforts for both staff and the customer, so most of the time there were many mistakes made which resulted in loss of customers and caused no customer satisfaction[Den08]. BRIEF STATEMENT OF EXPECTED SOLUTION The proposed solution is a full-fledged automated web-based management system that could answer all the troubles faced by Shift and Swift Company in the handling of shipment. The solution would comprise of an efficient data model to store and retrieve the necessary information about the entities available in the inventory or tracking the status of ordered items, etc. The system would also be having a user-friendly database so that even the people having less technical knowledge may handle the system effectively. Also, the provisions for producing the automated reports, financial analysis, etc would also be there to assist other departments of the organization as well[Den08]. PIECES framework No Symptoms P I E C E S 1 Mistakes could occur while issuing the invoice X X X 2 The communication among branches highly insufficient way to communication method? X X X X 3 Product tracking difficult to be confirmed X X 4 Hard to track due payment system X X X 5 No records are kept regarding the shipment X X X Problem Analysis CAUSE AND EFFECT ANALYSIS SYSTEM IMPROVEMENT OBJECTIVES Problem or Opportunity Causes and Effects System Objective System Constraint 1. The track of items coming-in and going out of the inventory was done manually 1. There were separate registers maintained for tracking the incoming items, current status of items, availability, etc and outgoing items. 2. No central record available to be accessed by the remote employees. 3. Errors and time delays in entering the information and retrieving the data. 1. Creating a reliable central database to track all the activities of inventory. 2. Data entry to be made through barcode scanning of items. 3. Standardization in identification of items. 1. Security issues. 2. Data to be protected from unnecessary usage on internet thus requiring an intra-net to be developed. 3. Provisions for proper updating have to be there. 2. Communication gap between the various entities in the supply chain and within the organization 1. Instances of miss-match between the materials supplied and records of entries in inventory registers. 2. Difficulty in dealing with the client especially when the delivery time, and expected delays, has to be mentioned. 3. Employees at the client’s side and other remote places have no idea of materials in inventory[Den08]. 1. Creating a central database client-server application that can be viewed simultaneously by different components of organization like receptionists, employees, ware house people, etc. 2. Live updates and tracking details to be sent to suppliers. 3. Online tracking of status of delivery of items in the processing. 1. Unreliability in the information if the details are being accessed during updates. 2. Creating an indirect access to the suppliers may be tough job. 3. Online tracking requires some part of database to be accessed on internet which could be a threat to the information security for inventory. 3. Difficulty in the generation of financial report, accounts, etc related to inventory management. 1. Manual paper-records make it difficult to make the accounting details, financial records, etc. 2. The records have to be converted into huge chunks of soft data which is then further processed for generating the required report. 3. This wastes a lot of time and resources. 1. Creating an extension of application for the accounts section. 2. Making sure that the transactions are reliable and updates are properly getting reflected on central server with no error. 1. The transactions are required to be made mutually independent so that more than one access is turned-down immediately by the server ensuring the security in transaction. Context Diagram Tentative List of Requirements Requirement Classification The system should allow drivers and managers to enter the information of inventory items in the field Functional The system should allow the employees to read the information from database Functional The system should make it easy for the employees having less technical know-how to use the system effectively and efficiently.  Functional The exact details of transactions and internal working of database should not be on internet ( Database in Internal LAN) Functional Shortage of some item, material, etc in inventory as per the demands of clients should be instantly updated on the server ( Need better sales forecasting) Non-functional The requirements of urgent items should be instantly updated to suppliers. Non-functional The access of application should be restricted as per the policies and norms of the company. ( Security Policy Need to be defined) Non-functional The system should have an access point at accounts department so that they may view and enter the accounting details. Functional System should be able to automatically generate the transaction details at the end of week, month and year. Functional Use-Case Glossary Initial model diagram Refined UML Use-Case Model Diagram Use-Case Narrative The use-case narrative shown here is of the view unresolved order described in the interview: Use case name: Ordering Scenario: Process customer’s order Triggering event Customer wants to place a new order Brief description The customer logs into the system and fills package information. The customer receives a receipt of the order details. Actors Customer Stakeholders Logistics, Accounting Preconditions Customer must be registered Customer must fill the order specifications Post conditions Order must be processed by the online system Order report must be generated Flow of Activities Actors System 1. Customer logins into the website 2. Customer makes an order by filling the package specifications 3. The customer views receipt 1.1 Systems facilitates user login upon verification 2.1 System verifies order specification 2.2 System processes order 3.1 System generates receipt Exception 1.1 Failed login 2.1 Order input verification failed Use case name: Picking Scenario: Picking of package. Triggering event Package has to be picked for transportation. Brief description The driver checks for the availability of packages to be picked and ensures the information is correct before receiving payments and picking Actors Driver Stakeholders Logistics, Accounting, Transport Preconditions Package information must exist. Package specification must be correct. Post conditions Payment should be made. Flow of Activities Actors System 1. Driver checks for available orders 2. Drives verifies the package information is correct 3. Collects payment and picks ups the package 1.1 Systems displays any package information available for the customer 2.1 System verifies or process changes effected by the driver 2.2 System processes order Exception 1.1 Package information does not exist 3. Payment not made Use case name: Generate payment receipt Scenario: Computer the receipt details of the payment Triggering event Customer has paid for the goods/service and wants a receipt Brief description This use-case describes the accepting the sales transaction between the customer and Shift and Swift. Actors Customer, Sales rep Stakeholders Logistics, Accounting Preconditions There must be payment of service There must have been some transaction Post conditions Payment has been made and settlement of the bill has taken place Flow of Activities Actors System 1. Customer logins into the website 2. Customer makes an order by filling the package specifications 3. He orders for the item 4. He pays 5. Gets receipt 1.1 Systems facilitates user login upon verification 2.1 System verifies order specification 2.2 System processes order 3.1 System generates receipt Exception 1.2 Failed login 2.1 Order input verification failed Use case name: Update list of packages Scenario: After some packages have been picked, it is important to update the packages that are still in stock Triggering event Some changes have taken place, either a new package has been picked or a new package has arrived Brief description This use-case describes the event of updating the available list of package that are in existence Actors Accountant, suppliers, warehouse Stakeholders Logistics, Accounting Preconditions There should be a package to be brought or picked Post conditions A package has either been added or subtracted Flow of Activities Actors System 1. The accountant and supplies gets to the system 2. They either order for a new package or facilitate the clearing of a another package 3. Processes the change 4. Finalize the process 1.1 Systems facilitates user login upon verification 2.1 System verifies package details 2.2 System processes package pickup or arrival 3.1 System updates the list Exception 1.3 Failed login 2.1 Order input verification failed Conclusion The system that has been described shows has been exhaustive and has looked into the various aspects of design. UML use cases are an important aspect of undertaking system analysis; it looks at the very aspects and how the system will be integrated and implemented. It is now clear how the system will function and the aspects that will be captured in the final design. References Den08: , (Dennis, Wixom, & Roth, 2008), Read More