Designing A Bespoke Solution, Commercial Of The Shelf Solution

The case identifies struggle and problem faced by organizations outsourcing IT projects and allows us to ponder on how to manage outsourcing well.

When in-house developing is the option Atrium chose they would be satisfying their uniqueness for their business, or to do less changes to their policies and procedures, and to meet the constraints of their existing systems and technology (Rosenblatt, 2014, p. 268).

The challenge is some of the past development work was done by a consultant. We have option to scale the current work which is not an industry standard and end up paying more money and band aids fixes or develop a new program that we can design and manage for our future growth knowing future growth is inevitable. The risk of continuing the current information system program is low for now, but it will be a major replacement issue for the future growth that could cost the company millions and lost business opportunities. Developing a new information system program is a risky choice from time

This way the IT department can understand what the higher level and lower level employees need for system stability and a better graphical interface. Another plan of action would include the method of Systems Development Life Cycle or SDLC. The phases of this method are planning, analysis, system design, implementation and operation. First we must plan on what exactly we are trying to accomplish. We know we need to upgrade the Riordan Manufacturing system. Next we must analyze the system and look for problematic errors. A project proposal can be essential to launching a system analysis (Farah, 2013). These are things to keep in mind: understand the business situation or problem, understand the significance to the problem in the organization, think of alternate solutions, the use of computer information systems for solutions, find people interested in the solving the problem (Farah, 2013). This plan is used to decrease redundancies, errors, and increase security. Finding all the weak spots in the company will help in the improvement of integrating an updated efficiently functioning system. Feasibility is important to account for when upgrading the system. Integrating a CRM will help to work with customers and understand their needs and wants to benefit the company and the relationship with their customers. Designing the system will involve knowing what kind of software is needed to store and

Requirement Traceability: Provide inputs to User stories, proposing the enhancements, review user stories written by business analysts and discuss with Business users to ensure all requirements are captured and provide

Requirements gaps: Making sure that the business is meeting its needs financially enough to use the software and if the software will increase profits.

With the correct use of Software Development Lifecycle principles and systems analysis tools they can offer significant savings in procurement and maintenance. The biggest motivation for using COTS components is that they will reduce overall system development costs and involve less development time because the components can be bought instead of being developed from scratch. This could prove to be useful for software development because of the ever increasing costs (Wikipedia, 2006).

Once the requirements are determined what the system must do, an analysis can be conducted to determine if it is more cost effective to develop the software in house or purchase commercial off the shelf software. In the analysis, both options should include the advantages and disadvantages of both approaches. If it is determined to develop the system in house each component of the system can be refined in detail in layers until they are detailed enough to validate the model of the new system. Utilizing a top-down approach can take advantage of new technology and development of the new system will help control development and cost and deliver a system faster, but the disadvantage of this approach is the system cannot be used until it is fully developed and tested. A bottom-up approach may take longer to develop but the system can be used after completion and testing of the first component, which the organization can see immediate results of the project and the new system can benefit the organization earlier on their

The company's strategic goals include increase in revenue and this goes hand in hand with increase in market share. One of the strategies employed by the company to achieve higher market share is offering complete solutions whereby the organizations offers products that are complementary to each other (CRM Editors, 2009). The company has different types of customers thus offering complementary products ensured best products are offered to different customers.

It is common knowledge that every one of the successful companies today sought and found a precise understanding of how it could create an advantage in the operations system and delivery options of the business organization in order to address detailed customer specifications. Every business person is determined to know what kind of work they would and would not do for their customers and in

|The intent of requirements engineering is to produce a written understanding of the customer 's problem. |

Some basic needs and requirement must be fulfilled by every human society for its survival. These basic needs or necessities for existence of a society are known as functional prerequisites of the society. The meaning of functional prerequisites is refer to the basic needs such as food, shelter and dress. This basic need is require for every individual to live his life. This is because, without them, human cannot remain alive. Functional prerequisites has some different between Islamic and Western sociologist.

 Baseline Business Requirements  Acquire Project Team  Create Project Definition Document  Develop WBS - Schedule  Develop

objective(s) are still needed to provide a starting point for the standard setter in helping to

It deals with the aspects of requirements life prior to its inclusion in the final requirement specification.