Aramex System: Analysis Of The System Requirements For A Business Problem (Coursework Sample)

4197350822960Day-December201500Day-December2015274320457200002743204023360Aramex00Aramex4629150-489839008Fall0008Fall8445509486900 HIGHER COLLEGES OF TECHNOLOGY00 HIGHER COLLEGES OF TECHNOLOGY2743209034145004298954983480Student Name (Student ID)Teacher Name: 00Student Name (Student ID)Teacher Name: -5594357879080Table of Contents TOC \o "1-3" \h \z \u 1.Analysis of the system requirements for a business problem: PAGEREF _Toc304236083 \h 21.2.Description of System Development Life Cycles used in project PAGEREF _Toc304236084 \h 21.3.Description of Fact-Finding Techniques used in requirement gathering process PAGEREF _Toc304236085 \h 21.4.List of User Requirements PAGEREF _Toc304236086 \h 32.Functional and Behavioral Model of the business system: PAGEREF _Toc304236087 \h 32.1.Create use case diagram of the system PAGEREF _Toc304236088 \h 32.2.Write use case description for use cases PAGEREF _Toc304236089 \h 42.3.Create activity diagram of the system PAGEREF _Toc304236090 \h 42.4.Create behavioral model of the system PAGEREF _Toc304236091 \h 43.Design of the business system: PAGEREF _Toc304236092 \h 53.1.Design user interface screens for all components of the system PAGEREF _Toc304236093 \h 53.2.Design relational database model for all components of the project PAGEREF _Toc304236094 \h 54.Structural Model of the business system:54.1.Create Class diagram of the system for all components of the system PAGEREF _Toc304236096 \h 64.2.Create Object diagram of the system covering all components of the system PAGEREF _Toc304236097 \h 65.Reference Page PAGEREF _Toc304236098 \h 66.Appendix Page(s). PAGEREF _Toc304236099 \h 66.1.Appendix 1: Fact-finding tools PAGEREF _Toc304236100 \h 66.2.Other relevant appendices (if applicable).6
Analysis of the system requirements for a business problem:
System requirements are the fundamental building blocks that are necessary to build a systems. They describe what the system shall do and its goal. System requirements are categorized into functional or supplemental requirements. Functional requirements are the things that a user needs to perform their work such as schedule pickup, track shipment among others while supplemental requirements maybe accuracy, availability, compliance among others. Functional requirements are based in the system design while supplemental requirements are based in the system architecture. The development of both functional and supplemental requirements are documented in the software requirement specification.
1 Introduction of the Problem Definition
1 Description of the system background
Aramex is a transport and a comprehensive logistic solution provider which was established in 1982 as an express operator which later transformed into a global brand offering good and satisfactory services. It is today trading on the Dubai financial market with more than 9000 employees in over 304 locations and 54 countries with a great and strong network with a good world presence. Aramex offers a wide range of services including international and domestic express delivery, logistics and warehousing, online shopping services and document management. Aramex is known for having been the first to release an audited sustainability report showcasing the commitment it has to its stake holders and community as well as the general environment.
2 Description of the problem statement
Making better decisions, enforcing policies, business management, easy communication, information security and safety, poor service delivery among others are some of the major challenges Aramex is facing due to lack of a good management system. With poor management and service delivery it is hard and difficult to offer fast and satisfactory services since most of the filing is manual and communication is not good. With a good system the company can be less worried about the customer’s feedback and requests as well as their partners and associates since information can be received in real time compared to the traditional methods.
3 Description of proposed solution
Being a company with many customers, employees and stake holders, Aramex needs a system that can be able to simplify daily tasks, reduce response time, increase productivity, allow resource sharing with their employees and provide enterprise collaboration among other services. It is hard to work blindly without a system that can pass information to customers on their products, shipments, pickup locations, payment rates and office locations. Aramex needs a system that will help increase efficiency, consistency, trust and a system that is available and easier to use both for the end user, customers and the stake holders boosting productivity. Among the benefits that comes with a good system is that it allows convenient service, fast and easier communication with inter branches, secure distribution and information management services, inter relationship between the company and its customers is improved, easier consultancy, real time data when required, reduced risks in the daily activities and greater productivity, easier control and quick planning. It will be a system that can store all information under one roof in a data base and a system that is up to date, fast and efficient and of high performance measurement and responsibility to the company its customers.
Description of System Development Life Cycles used in project
SDLC is the process in which it is determined how an information system can be made to support business needs through designing a system, building it and delivering to the users. There are two different SDLC that are used in system analysis and design such as water fall model, iterative model, the spiral model and the V-shaped model. I chose to use water fall model because of its advantages among them being that it is simple and easy to use, easy to manage, phases are completed each after the other and also works well for smaller projects that are easily understood. It has six phases which are analysis, requirement specification, design, implementation, testing and integration and operation and maintenance.
30988035052000
Waterfall Model
Description of Fact-Finding Techniques used in requirement gathering process
Fact finding is the process of collecting data and information which are based on techniques that contain sampling of documents, analysis, research, questionnaires and interviews, joint requirements planning and prototyping. In the analysis of the system I used some fact finding techniques such as sampling of existing documentation forms and databases for analyzing the already existing system and documentation such as emails, customer feedback and complaints, notes in the suggestion box among others, questionnaires, interviews, prototyping which is used for sampling a small working model of the system and joint requirement planning.
I formulated some questionnaires that I distributed and then scheduled an interview indicating who would be interviewed and when. Among the people interviewed would be the sponsors of the project, business users, project team members and any other member in the organization. I had written questions ready for the interview. With the different answers from the interview and the questionnaires I will have a clear picture of what the system should look like. There were challenges since some of the members did not comply or attend the interview in time and a lot of time was wasted waiting for them to attend the interview and also some of the questionnaires were poorly answered.
Include a copy of the Fact-Finding tool that you used (e.g. questionnaire / interview questions) in the project report appendix.
You do not need to conduct the actual interview and you may include information from your imagination but the included information should align with your project.
Refer to chapter3 (Requirements Determination) of textbook to have a better understanding to fact-finding techniques.
List of User Requirements
User requirements are used as a tool to understanding what is required of a system and to help set a development channel or path. They indicate why the user needs the system, what they user must achieve from the system. With the user requirements it will be easier to write a documentation that will be used in refining the system requirements. Below are requirements I gathered during the interview and from the questionnaires.
1 The system should be able to assign an order to a certain shipment company.
2 The system should offer a place where a customer can chat direct with the help desk
3 The system should be able to update information directly to the system for the use in other branches of the company in different places.
4 The system should protect the customer’s privacy and offer confidentiality.
5 The system should be easier to learn and use.
6 The system should be robust to allow multiple usage.
7 Retrieval of information should be fast and effective
4 List of functional requirements
* Easier data processing and record management
* Protection of user information
* Real time feedback
* Services updates
* Request offer
* Locate officers
* Calculate rate
* News
* Schedule pickups
* Prepare shipment
* Track shipment
5 List of non-functional requirements
* Accessibility
* Efficiency
* Privacy
* Fault tolerance
* Quality system
* Reliability
* Consistent
* Fast
* User friendly
* Easier maintainability
* Robust
* High stability
6 List of Usability requirements
* Understandability
* Operability
* Learnability
* Attractiveness