The Concept of The Clothing Store ABC - Assignment Example

?Introduction A clothing store, ABC, has contacted a software company to deploy a software program which will help them in supporting their Sales method. Being a software engineer, I have gathered the following requirements from the scenario presented by the clothing store. The system will be designed for 4 types of stakeholders. Customers will be the the buyers of the products. Salesperson will be dealing the customers and will be responsible for handling the initial computations of the system. Accountants will be using the information generated through the system to produce sales reports and forward them to the appropriate people. Manager will hold administrative rights and will only be generating administrative orders. The designed software will minimize the need of paper work at the company. A centralized database will be deployed which will remove many issues such as maintaining records twice or inconsistent data. Through database techniques such as transaction roll back, recovery and cascade delete/update, the system will always contain updated and valid data. RUP alongwith UML has been used to design the software. RUP is based on UML and it ensures the production of a high quality software which meets the need of the clients and the users within the alloted time and budget. Part 1 – Development Plan 1. Requirements: Analyze Problem: The clothing store, ABC, wishes to transfer the business logic on a computerized system in order to support the sales of the store Understand Stakeholder Needs: -Identify Stakeholders: Customer, Salesperson, Accountant Admin/Manager Identify Requirements: Salesperson: -Create a Ticket -Modify a Ticket -Remove the Ticket -Compute Bill -Generate Bill -Check for the availability of an item in the stock -Check the price of an item -Save Bill in the Customer File Record and mark as new -If exchange/Return order generated from the manager, confirm return/exchange based on the bill ID (which could be easily found through a linear search in the customer file record) Accountant: -Update stock cards automatically through Customer File Record using the new bills and marking them as old -Generate Sales Report -Send Sales Report to appropriate people Manager: -Generate Exchange/Return Order on a Customer Bill ID 2. Analysis and Design: Analyze and design the system to be a feasible solution -Economic feasibility: The system should be designed within the allotted budget and time -Operational feasibility: The transactions are secure and cannot be tampered. The transactions can be rolled back, in case of a return back of an order. -Technical feasibility: Software, hardware and network issues should be as less as possible. 3. Implementation: Follow Best Practices 4. Testing: Develop Test cases and test the system against the following features: -Functionality: Does it provide the correct functionality? -Reliability: Is the system free of defects and fault tolerant? -Performance: Is the system’s flow smooth enough to be run easily as a daily process? 5. Deployment: -Deploy the system -Provide user manual for the system -Release Documentation for further maintenance of the system -Develop training sessions Part 2 – Use Case Model Create a Ticket: Usecase Create a Ticket Actor Salesperson Purpose Enter Details about a Product Overview Whenever a new product is taken to the store, a new ticket will be created for the product in which its details will be listed. These tickets will help the customers in instant shopping. Type Primary Cross Reference A new product with no ticket must exist in the stock Actor Action System Response 1. Click on create ticker Return a ticket interface 2. Fill details and enter Save Validate details and show confirmation message Check Price: Usecase Check Price Actor Salesperson Purpose Check the price of an item using the ticket Overview On the request of a customer, any item’s price can be checked through the system immediately using the tickets Type Primary Cross Reference Create a Ticket Actor Action System Response 1. Open Ticket Return the details of the specified ticket 2. Check for price Return Price Part 3 – Communication Diagram Explanation: -Create New Ticket: The salesperson calls a method of the Ticket Class. After the method has been executed, it moves to the next iteration. Another method of the ticket class is called. The same is repeated for the next step. At the end of the communication cycle, a ticket has been created, details has been filled in and it has been saved into the database -Check Price: The Salesperson calls a method with a parameter of the ticket class. The Ticket class, in return, calls a method of the Price class which shows the price to the salesperson in the user interface Part 4 – Class Diagram Explanation: 5 main Dominant classes of the system have been identified. The letters 1 and n identifies the relationship of the classes with each other. A Ticket is created for each of the products available in the Stock. More than one ticket can be used to compute one bill. A bill is used to update the stock card based on the status of the bill. Many bills are used to generate two types of reports, which can be later on sent forward or printed. Part 5 – Development Process Below mentioned development process will be carried out for the further development of the software -A Centralized Database will be made. Tools such as MySql can be used to create and maintain a Centralized Database. -Database tables and the relationship among them can be designed using the tool DB Designer. The tool will normalize the tables and generate SQL for them which can be imported in the MySQL Database. -A Web Portal will be made which will be accessible by the authorized persons from any location. A web portal can be created from scratch using PHP, HTML and CSS. Another alternative is to build a web portal on a framework such as Joomla or Drupal. -Authorized people will be able to access the portal concurrently without effecting the transactions of the other people logged in the system -Security will be implemented in the system in order to prevent the database from malicious attacks. Threats such as SQL injection will be kept in focus. Part 6 – User Interface Conclusion: The designed system will help the clothing store, ABC to enhance their sales as the sales process will become efficient affecting the customer service of the store. The need of paper work will be removed and the system will always contain valid and updated data. The designed interface follows the guidelines of Human Computer Interaction. The interfaces are simple, visible, efficient and usable. Separate access will be provided to different type of the users of the system. For example, salespoerson will have create only rights, such as create a ticket or modify a ticker whereas Managers will have complete administrative rights to the system, such as delete a tocker or generate an order. Security is a critical issue in the softwares. The software must be designed, keeping in mind the guidelines of the security. Techniques such as sql injection prevention and encryption of passwords and important data must be used while building the software. The software must comply with the guidelines of a standard software development process. References Tools Used: Use Case Diagram: Microsoft Visio Class Diagram: Microsoft Visio Communication Diagram: Microsoft Visio Interface: Balsamiq Read More