Club It -- Part Three Thesis

PAGES
3
WORDS
1018
Cite

This information can be provided to the marketing and scheduling teams first, so that they can devise a program of events, specials and menus and pricing that will maximize profitability. This information, along with sales expectations, can then be passed along to purchasing, who can work with the supply chain to reduce the club's inventory on hand, getting deliveries as they are needed. Thus, internal stakeholders to be interviewed would include marketing, the kitchen, the head bartender, the entertainment director, accounting and purchasing. Each must be brought into this coordinated effort. External stakeholders would include the major suppliers, in particular for the food and drink categories. They must be aware of the changes that we are making and we must make changes that fit within their capabilities or the system will not have the intended effect. d. This project will go through the ten phases of the systems development life cycle. The initiation has begun, as Club IT has determined it needs to improve profitability. The concept development stage will determine the nature and scope of the project -- i.e. The areas of focus for the project. In terms of planning, the project will require management to determine the resources required and ensure that those resources are available. The end users, Ruben and Lisa, must then break down the specific requirements that they have for the system -- the information that they will need in order to achieve their objectives. The design function will be done by the IT professional, in order to determine how the information will flow...

...

Development then takes on the form of the IT professional either adopting and adapting an existing dashboard system or developing a new one from scratch. The system will then be tested by the managers to ensure that it meets their requirements, and to gather feedback. Once the system has been determined to be ideal, it will then be implemented. The next step will be Ruben and Lisa working with the system, providing in-process reviews of the system and the IT professional working with them to maintain and improve the system. Lastly, management and the IT professional will work together for the disposition phase, where the presentation of end data is determined. This project fits with this life cycle well because management has determined its objectives and the specific information needs. Once the system has been developed, Ruben and Lisa will begin to work with it in order to ensure that these needs are being met and that there are no other needs that could be included. Once the system is fully implemented, they will be able to determine how effective it has been with respect to helping them achieve their cost reduction and revenue maximization objectives.
Works Cited:

iExecutive Dashboard website. Retrieved July 18, 2009 from http://www.iexecutivedashboard.com/solution/index.html

Kirtland, Alex. (2003). Executive Dashboards. BoxesandArrows.com. Retrieved July 18, 2009 from http://www.boxesandarrows.com/view/executive_dashboards

Ecora website. Retrieved July 18, 2009 from http://www.ecora.com/ecora/products/incomand.asp

Sources Used in Documents:

Works Cited:

iExecutive Dashboard website. Retrieved July 18, 2009 from http://www.iexecutivedashboard.com/solution/index.html

Kirtland, Alex. (2003). Executive Dashboards. BoxesandArrows.com. Retrieved July 18, 2009 from http://www.boxesandarrows.com/view/executive_dashboards

Ecora website. Retrieved July 18, 2009 from http://www.ecora.com/ecora/products/incomand.asp


Cite this Document:

"Club It -- Part Three" (2009, July 18) Retrieved April 25, 2024, from
https://www.paperdue.com/essay/club-it-part-three-20517

"Club It -- Part Three" 18 July 2009. Web.25 April. 2024. <
https://www.paperdue.com/essay/club-it-part-three-20517>

"Club It -- Part Three", 18 July 2009, Accessed.25 April. 2024,
https://www.paperdue.com/essay/club-it-part-three-20517

Related Documents

Systems Development Life Cycle has historically been a very useful tool in the development of software and operating systems in Computer Information Technology. Through the Systems Development Life Cycle there are at least five distinct phases that are delineated and performed within a linear patter. Meaning, that each step must be complete or at least very close in order for the next set of experts to begin the next phase

However, the company did feel it should develop its own Database infrastructure that would work with the new underlying database management system and would mesh with existing organizational skills and the selected enterprise software solution. Because the company followed a standardized implementation process, they were able to successfully reengineer their existing business structure. The objective of the System Development Life Cycle is to help organizations define what an appropriate system

system development life cycle (SDLC) approach to the development of Information Systems and/or software is provided. An explanation of SDLC is offered, with different models applied in implementing SDLC delineated. Advantages and disadvantages associated with each of the models will be identified. System Development Life Cycle According to Walsham (1993), system development life cycle (SDLC) is an approach to developing an information system or software product that is characterized by a

Systems Development Life-Cycle is a framework for an evolution from abstract ideas to a concrete reality Systems development life-cycle (SDLC) is a structured process of systems development is an evolutionary process that proceeds from a broad concept of information requirements and finally ends into the manufacturing of a product -- development of a new system. From this conception it can be seen that the ideas of SDLC begin to narrow

Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only

This process places the user in a central position for both determining system requirements and ensuring they are met. The benefits of these systems include not only improvements in user efficiency, but also others, such as reduced training costs, reduced user errors, reduced maintenance costs, and increased customer satisfaction. However, the chief requirements in these kinds of systems become to understand the users' information needs. As we argued earlier, the systems