Creating a Customer Information System for the York Bikes Company

A Computer Software Engineer develops software systems to be used by their clients, such as a website used to sell the client’s products. Although software engineers spend the majority of their time programming and testing the software, a key component to the success of a software engineer is the ability to write a thorough Software Requirement Specification (SRS). A SRS documents the requirements and dependencies needed for the software, prior to beginning any programming. Therefore, a Software Engineer must po The SRS is so important because engineers can have a wide scope of clients that they regularly work with.

Requirement Engineering understands the needs of users, customers and stockholders and develop technologies to address specific stockholder requirement tasks like elicitation, modelling and analysis to implement software system.

Step-1: Determine the purpose of the meeting: Before a meeting takes place, the purpose of the meeting should be determined. All the participants should be informed about the purpose of meeting beforehand, so that they come prepared and can contribute more.

Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).

The commonly used methods of observation, interviews, etc., can help analysts pinpoint exact requirements based on user input and business processes. According to Charvat (2003), “One of the biggest benefits of a proper user requirements specification is that you'll be able to plan and estimate your project correctly, decreasing the chance of cost and time overruns.” The analyst must listen to the employees and gain a thorough understanding of all business processes before establishing the new system requirements.

When implementing an information system, an organization must take steps to ensure the company is making the right decision. The most important step or decision when acquiring a new information system is making sure the system will accomplish and meet the organization goals. Stakeholders play a major role in the process of acquiring a beneficial information system and making sure it is the best choice for the organization (Ruffin, 1995).

Acknowledge the participants when ideas are spoken. Thank them for their input. Allow participants to put something on the agenda either before the meeting or for the next.

The description of the requirement is very important in the process of acquiring an information system, stating of sections it intends to function, opportunities and problems it may arise during adoption stage (Bernroider, 2008). The description is as important

A Request for Proposal is used when the agency can specifically define the requirements of the group of commodities, or contractual service being sought and can describe the deliverables. Criteria such as price, prior experience, and the vendor’s project plan, should be weighted and scored by evaluators; unlike the Invitation to Bid, the contract is not awarded automatically to the responsive bidder with the lowest price, but must be awarded to the vendor who provides a solution that is “most advantageous to the state,”

Sealed bidding is the means by which government contracts competitively when requirements are clear, accurate and complete. An Invitation for Bid (IFB) is typically used when the scope of work or project specification is well defined; payment will be based on a lump sum or per unit basis and no discussions or negotiations are required (Koch, 2012). Examples of IFB services include trash and debris removal, oil testing services, parking lot sweeping, recycling services.

(tk) There are many guideposts for an effective meeting; these include but are not limited to: (list). By its nature, this working paper is not meant to be exhaustive; we will therefore focus on one CSF of a successful meeting the agenda.

In this phase the company’s define their requirements in terms of what information is needed? Why is it needed? When is it proper?

Enterprises seeking a consulting firm or product vendor for management, strategy, outsourcing, software implementation, change management, or a host of other reasons issue a request for proposal (RFP) to elicit bids for services or products from vendors in the form of a responding proposal. The RFP process is a means of bringing structure and transparency to the procurement decision and the process allows both the client and potential vendors to vet each other to determine if they are suitable business partners. Before an organization issues the formal RFP to potential vendors, the organization completes several steps.

While ABC maintains a small information technology (IT) group, the expertise does not currently exist internally to design, build, and implement the sort of extensive online platform required for this effort. Therefore, the recommendation is to contract this work out to an internet marketplace provider who can work with ABC to meet its needs within the determined timeframe and budget. It should be noted that while ABC does not have this expertise internally, the technology exists and is in use throughout the marketplace which lowers the risk of this concept considerably.

User requirements: It provides the details of services required under which the system must operate smoothly.