Professional Documents
Culture Documents
BSCPE 5201
CONSTRAINTS CHARACTERISTIC
The system should have a modular design Future, internal, and desirable
if possible
All expenses from now on must be Future, external, and mandatory
approved in advance
2. Explain why it is important to define the payroll project’s scope. Explain how to define project scope.
It is important to define the payroll project scope because it is very necessary to define the boundaries of
this project for knowing its benefits as well as limitations. It is also helpful in knowing the requirements of
the system
Project scope is related to the specific boundaries for the particular project. According to some business
analyst is very helpful to determine the scope of the project by the list of following which are as follows:
Must Do
Should Do
Could Do
Wont Do
This list is reviewed during system analysis phase when user is developing the system requirement
document
4. What topics should be included in a report to management at the end of the preliminary
investigation?
Introduction
System request summary
Findings
Cause for action
Project role
Time and cost estimate
Expected benefits
Appendix
Strategic planning is defined as the process for identifying the strategies, long term goals and the
resources of the business. The IT team will be able to focus on the implementation of the new system by
understanding strategies planning process.
Strategic planning firstly use SWOT analysis for finding the strength, weakness, opportunity and threats
to the a system and then clarify the mission statement for the new system and also define the goals for
the new system. The Way Out's owner had no long term plan for their company. When the owner of the
Way Out was asked about their long term plan then she replied that she is not thinking beyond one year
time frame.
2. Decide what else you might want to know about Way Out. Consider the internal and external factors
described on pages 59 to 61, and make a list of questions to ask the owner.
To be competitive, we must use all corporate resources, including IT resources, to produce the greatest
possible benefit for our company and our stakeholders. We believe that the best strategy is to create a
systems review committee (SRC), with one representative from each major department. The SRC will work
as a team to review systems requests, set priorities, and oversee IT projects across the company. In order
to avoid any departmental bias, the committee will select a chair, who will report directly to the president
2.Write a memo to your boss explaining potential disadvantages of the committee approach.
You should explain to your boss, even where a systems review committee is in place there are
disadvantages that have to be considered. The IT director usually serves as a technical consultant to
ensure that committee members are aware of crucial issues, problems, and opportunities. Action on
requests must wait until the committee meets to discuss. To avoid delay, committee members use
memos, e-mail, and teleconferencing to communicate with each other. Another potential disadvantage
of a committee is that members might favor projects requested by their own departments, and internal
political differences can delay important decisions.
3.Draft a set of ground rules for committee meetings. Try to suggest rules that will minimize political
differences and focus on the overall benefit to the company.
System request requires the information that help to identify the issue, specify the priority order, and
define initial feasible solution. We need to set the following rules the question should specify the need of
change in current system and urgency of the request. The requester should explain the problem and try
specify feasible solution.
4.Most people serve on a committee at some point in their lives. Write a brief memo describing your
committee experiences, good or bad.
Ineffective, unproductive or simply “bad” committee meetings are very easy to recognize because they
have some or all of the following characteristics:
they feel like the meeting goes forever but nothing was actually achieved
conversations drag on, bouncing from one point to another with little focus on the issue to be
discussed
conflict occurs regularly with committee members often being accused of having their “own
agendas”
nobody really understands what each other is doing and often feel they are the only person
doing any work
nobody, except the Treasurer, has any idea on the financial position of the club and no matter
how many times people request financial information it doesn’t appear, or if it does it is simply a
bank balance
people turn up to the committee meetings with little idea on the topics to be discussed
anybody with a contrary view to the dominant committee members are made to feel like they
are trouble makers
Will the system interface properly with external systems operated by customers and suppliers?
Does the combination of hardware and software supply adequate performance?
Does the proposed system have clear expectations and performance specifications?
Will the system be able to handle future transaction volume and company growth?
2.Provide three sample questions to determine whether a project has operational feasibility.
4. Provide three sample questions to determine whether a project has schedule feasibility.
Will the new hardware be available before the deadline date for the project?
Is the network going to be ready do system development can start working on the project?
Is there anything that will cause an unacceptable delay in the launch date for the project?