Download System Analysis And Design Project UAENative and more Assignments System Analysis and Design in PDF only on Docsity!
System Analysis & Design
Assignment 1
Submitted by: Ramsha Ansari, 201811033 PART 1 SWOT ANALYSIS: Strength: They have a variety of native products. The main business has 50% of sales and 50% of profits. Annual sales of AED 3M, which is increasing at a rate of 3% per annum. Net profits of 8% of total sales. All in all, they have great product knowledge, quality, and excellent capital situation. Weakness: Supplier relations are all paper-based transactions, which is inefficient as it is time- consuming. Also, poor company operations and limited project resources and skills. Opportunity: Calling in a new IT consultant can be a plus. Can expand their retailers. Threat: Poor company operations as a supply chain management system is yet to be developed and implemented. Unable to consume more than half of next year’s business. Competitors can have a better functioning supply chain. A single source of supplier is also a threat. ASSESSING REQUEST FEASIBILITY: Operational: The company must assess if the project is supported by the management, and if there are any ethical or legal issues to be considered before implementing a new system, and if the new system may result in a workforce reduction. One of the main pieces of supply chain management software is the measurement of supplier relationships. Many supply chain management systems provide features that allow users to compare supplier costs and support structures. These operational advantages allow managers of the supply chain to make meaningful choices with which suppliers to form partnerships. Economical: In this phase, the budget management and budget planning are performed, and the company assesses the cost and benefit of the new project/system. Companies with a highly established supply chain infrastructure can trade many goods easily and at low cost between companies and customers. This is the prime economic benefit. Technical: Assess if the company has the necessary hardware, software, and network resources required to implement the new project if the staff has the knowledge and expertise to utilize the new system and if prototyping will be required for the system. We see helpful additions such as mobile connectivity being included in more and more frameworks as
technology continues to evolve. Today managers of the supply chain will be on the move but still linked to the critical processes of the day. It reduces costs and increases efficiency by automating processes, expansion of sales areas, providing new possibilities for communication Schedule: Assess if this project can be implemented in the timeframe provided by the management. WORK BREAKDOWN STRUCTURE: Breaking a task into smaller tasks is a standard technique for efficiency that makes work easier to handle and available. The Work Breakdown Structure (WBS) is one of the most relevant project management documents that use this technique. It uniformly combines scale, cost, and timeline baselines to ensure the project schedules are compatible.
Effective system requirements gathering requires practice and persistence. It is a critical step in the process of software creation and deployment. If the correct requirements are not met to allow users to find value in the system, the acceptance of users will be lower, and the project will fail. The documentation of techniques that will be used for gathering system requirements are: Interviews: Interviewing is a worthwhile approach used in the compilation of software specifications. E-meeting is an efficient way of interviewing in many cases. The interviewer and interviewee, including other application screens, reports, mock-ups, and outlines, will share screens and content. They should be well thought about and organized before they sit with the interviewee to help them get the best out of the interview. The analyst must identify interested parties who must be interviewed. This could be users communicating with the existing or new framework, administrators, project financers, or everyone else involved. It is important to ask open questions and closed questions when preparing for an interview. Open questions typically help to collect useful knowledge based on different people and how they communicate with or interpret the system differently. Document reviews: The study of existing documents will prove to be a useful technique for collecting requirements on its own, as well as using it to complement other techniques. The analyst can help explain the company, or procedure, and its current state by reviewing the current process and documents. Existing documents would send the titles and names of stakeholders involved in the framework to the analyst. This will help the analyst formulate questions to obtain additional criteria for interviews or questionnaires to ask stakeholders. This may also assist the analyst in asking these questions during interviews if an analyst is confused about why such protocols are in place. Analysts can discover problems that they can discern on their own when studying the requirements. In old records, the analyst could find that there was missing information. Redundancy, in which measures are excessively repeated, can also be identified. The consultant may review the old requirement documents and re-use the still valid requirements while removing those that are outdated. A review of documents will discover standards and guidelines for the organization itself. Documents for analyzes may be used as an alternative to information collected from the interviews, surveys, and feedback. For example, if any of the responses to the interview are ambiguous, organizational records may help to clarify the answers of the individual. Existing documentation can also enable the analyst to understand why such activities are done when observing them. Any records that could be obsolete are disadvantaged and the analyst needs to check whether the documents are up to date. Another downside of paper analysis is that it can take very long. Brainstorming: It is an important technique of requirement gathering to find solutions to problems. Brainstorming can be performed independently or in groups. The collected ideas can then be analyzed and integrated into the system specifications where appropriate. Ideas may be extracted from what users and stakeholders saw or had learned elsewhere. This can be useful in
identifying their criteria for users and stakeholders. Disadvantages: When needed to do so, people cannot brainstorm ideas easily. Some people find it much harder than others to brainstorm. REQUIREMENTS ANALYSIS: Requirements Analysis is the procedure by which the users' expectations of any system to be built or modified are defined. It comprises all the tasks carried out to determine the needs. Therefore, it is the process of analyzing, documenting, and validating software or system requirements and managing them. There are different techniques used for business Requirements Analysis such as: UML (Unified Modeling Language) Diagrams Flowchart technique Data flow diagrams Gantt Charts DFD (DATA FLOW DIAGRAMS): This approach is used to visually depict processes and structures that are complicated and difficult to explain in text. The flow of information through a process or entity is described by data flow diagrams. It also includes the inputs and outputs of information, data stores, and the different subprocesses by which the information passes. With the assistance of uniform notations and symbols, DFD defines different entities and their relationships. It is easier to find any shortcomings by visualizing all the elements of the system. In a bid to create a robust solution, these weaknesses are then removed. It is used as a preliminary step to create an overview of the Supply Chain Management without going into great detail, which can later be elaborated. It normally consists of overall application dataflow and processes of the Supply Chain Management process. It contains all of the user flow and their entities such as all the flow of Supply Chain, Customer, Retailers, and Suppliers. All of the below diagrams have been used for the visualization of data processing and structured design of the Supply Chain Management process and working flow. DFD Diagrams of the UAENative Company are depicted below. Context Level Diagram of UAENative’s Supply Chain Management System:
DFD Level 1 then goes one step deeper into parts of Context Level of Supply Chain Management. It may require more functionalities of Supply Chain Management to reach the necessary level of detail about the Supply Chain Management functioning. The 1st Level DFD contains more details of Supplier, Manufacturers, Retailers, Product, Customers, and Warehouse. UML (UNIFIED MODELING LANGUAGE): UML consists of an interconnected series of diagrams generated to define, visualize, build, and record a system's objects. It is a valuable tool in the development of object-oriented applications. In UML, to reflect the architecture of a software project, graphical notations are used. UML helps verify the software's architecture as well. Class Diagram of UAENative’s Supply Chain Management System:
Sequence Diagram of UAENative’s Supply Chain Management System:
Use Case Diagram of UAENative’s Supply Chain Management System:
CONCLUSION
