GUIDELINES FOR GIT BUSINESS CASE

COMPANY SELECTION:

The goal of every company is to acquire a high profit margin, good market share while minimizing costs
for their operations. Along the way, most companies encounter problems that hinder them from achieving
their goals. Some problems can be answered by simply allocating more budget for human resources,
hardware or software upgrades, other problems would require more than the above mentioned solutions.

The selection of a company should encompass a solution that would involve the use of a system. A system
has components (data, people, hardware, processes, and software) that work together. There are
feasibility factors that can be assessed for the selection of a company: problems encountered, proposed
number of users, company and operation size.

The problems encountered should be more than just hardware and software upgrades; the number of
users for the proposed system should benefit the entire company and the customers, not just one or two
personnel; the target company’s operations should be large enough to have a good market share in the
industry they are in.

DOCUMENT CONTENT

PRELIMINARIES:

Cover Page (see attachment)

Acknowledgement
Paragraphs which express gratitude towards people or institutions that have helped or have provided
valuable contributions in the implementation of this project

Table of Contents
Roadmap to each portion of the document, from the preliminaries to the attachments. Use automatic
table of contents generated through MS Word

CHAPTER I: COMPANY OVERVIEW

Company Profile
A professional introduction about the business operations of the company. Informs the audience about its
products, services, and current status. It sums up the business plan of the company, how it came about
(history) and the reason the company is in that business venture.

Mission of the Company

Defines a company’s goal in three important ways: what the company does for its customers, what the
company does for its employees, what the company does for its owners.

Vision of the Company

Describes where the company aspires to be upon achieving its mission, states the desired future position
of the company.

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
 Organizational Chart
A diagram that visually conveys a company’s internal structure or hierarchy by detailing the roles,
responsibilities, and relationships between personnel within an entity.

Figure 01: Sample Organizational Chart

Business Rules
Paragraphs detailing the rules and constraints of the business. Describes the operations, instructions on
how certain day-to-day actions should be performed.

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
 Business Process
Paragraphs detailing a collection of linked tasks which find their end in the delivery of a service or product
to a client. These are sets of activities and tasks that, once completed, will accomplish an organizational
goal. The business process discussed here should be about the current system applied by the company.

Business Process Diagram (flowchart)

A graphical representation of the steps discussed in the previous section will be shown using the proper
flowcharting symbols. The steps are in a sequential order and presents the workflow of the current system
of the company.

Figure 02: Sample Flowchart

CHAPTER II: SYSTEMS ANALYSIS

Problems Encountered
List of problems encountered by the company with a brief description on their effects. At least three (03)
major problems and should be discussed. An example is shown below:

Miscomputation of time sheets, wages, taxes, and issuing checks

The company does not apply segregation of duties. The clerk in-charge of checking
attendance of employees is also the personnel who computes for the wages and
deductions of the employees. The clerk has too many responsibilities and has limited time
to accomplish such responsibilities that brings about errors in the computation of the
wages.
Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
 Proposed Solution
A detailed description on what the proposed system would be, how the proposed system would address
the problems stated in the previous section and all needed components of the system. This section contains
the new processes formulated, the data to be gathered, the people involved and other minute details
regarding the proposed system.

Functional Requirements
Defines the intended behavior of the system or its components. It describes the functions a system must
perform or do which addresses the users’ needs. A function is nothing but inputs, its behavior, and outputs.
It can be a calculation, data manipulation, business process, user interaction, or any other specific
functionality which defines what function a system is likely to perform. The figure below states some
examples of functional requirements for a human resource information system.

Figure 03: Sample Functional Requirements for an HRIS

Non-Functional Requirements
Requirements which describe the general characteristics of a system, also known as quality attributes.
These requirements are connected to other issues, such as hardware capability and budgetary constraints.
Represents a set of standards used to judge the specific operation of a system. A non-functional
requirement is essential to ensure the usability and effectiveness of the entire software system. Examples
of non-functional requirements are: network bandwidth, costs, flexibility, and reliability.

Scope and Delimitation

The scope identifies what topic and areas the researchers intend to cover in terms of the system being
proposed. The scope contains the explanation of what information or subject is being analyzed. It is
followed by an explanation of the limitation of the research. Research usually limited in scope by sample
size, time and geographic area. While the delimitation of study is the description of the scope of study. It
will explain why definite aspects of a subject were chosen and why others were excluded. It also mention
the research method used as well as the certain theories that applied to the data.

Feasibility Analysis
A feasibility study is an analysis that takes all of a project's relevant factors into account—including
economic, technical, operational, and scheduling considerations—to ascertain the likelihood of completing
the project successfully. Project managers use feasibility studies to discern the pros and cons of
undertaking a project before they invest a lot of time and money into it.

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
 Schedule – assessment of the duration of the system development. System analysts have to
estimate how long the system will take to develop, and whether all potential timeframes and the
completion date schedules can be met. A Gantt chart will be utilized to express this.
Technical - evaluate whether the new system will perform adequately and whether an
organization has ability to construct a proposed system or not. The technical assessment help
answer the question such as whether the technology needed for the system exists, how difficult
it will be to build, and whether the firm has enough experience using that technology.
Operational - assessing operational feasibility is to gain an understanding of whether the
proposed system will likely to solve the business problems, or take advantage of the opportunities
or not. It is important to understand how the new systems will fit into the current day-to-day
operations of the organization.
Economic – used as a method for evaluating a new system or project, also known as the cost
benefit analysis. Comparison of costs of the current system with the proposed system are
calculated. Costs are subdivided based on categories of these costs: development and
operational. Once the costs have been calculated, the benefits are then
Return on investment (ROI) equals to net cash receipts of the project divided by the cash outlays
of the system. Companies choose the system that provides the highest ROI. Study.com has
provided the basic ROI formula, ROI = (Net Profit / Total Investment) * 100

You are a house flipper. You purchased a house at the courthouse auction for $75,000
and spent $35,000 in renovations. After sales, expenses, and commission, you netted
$160,000 on the sale of the renovated house. What is the ROI?

Your net profit is going to be what you netted ($160,000) minus what you spent ($75,000
+ $35,000), so it is $50,000. Your total investment is also what you spent ($75,000 +
$35,000), which is $110,000.

ROI = Net Profit / Total Investment * 100

ROI = 50,000 / 110,000 * 100
ROI = .45 * 100
ROI = 45%

If only house flipping was that easy. Keep in mind that you can certainly lose money on
an investment. If there is a loss, the formula will yield a negative number. Here's a simple
example:

ROI = -1,000 / 5,000 * 100

ROI = -0.2 * 100
ROI = -20%

Payback period (PP) is amount of time required for an investment to generate sufficient cash
flows to recover its initial cost. There are two ways to calculate the payback period, which are:
averaging method and subtraction method.
Averaging method. Divide the annualized expected cash inflows into the expected initial
expenditure for the asset.
Subtraction method. Subtract each individual annual cash inflow from the initial cash
outflow, until the payback period has been achieved.

Benefits are subdivided into tangible and intangible. Tangible benefits are those measured in monetary
terms (with computation) and intangible benefits cannot be measured in monetary terms but they do
have a very significant business impact.

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
CHAPTER III: PROPOSED SOLUTION MODELING

Decomposition Diagram
Explains the breakdown of processes within a project or business area or functional area. The purpose is
to show all the processes and identify relationships and dependencies among them. Note that a
decomposition diagram doesn’t drill into the how; it merely outlines the what.

Figure 04: Sample Decomposition Diagram

Context Diagram

A visual representation of the proposed system under consideration as a single high-level process and then
shows the relationship that the system has with other external entities (systems, organizational groups,
external data stores, etc.). A context diagram, sometimes called a level 0 data-flow diagram, is drawn in
order to define and clarify the boundaries of the system. It identifies the flows of information between the
system and external entities. The entire software system is shown as a single process.

Figure 05: Sample Context Diagram

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
 Level diagrams of the system
As described previously, context diagrams (level 0 DFDs) are diagrams where the whole system is
represented as a single process. A level 1 DFD notates each of the main sub-processes that together form
the complete system. We can think of a level 1 DFD as an “exploded view” of the context diagram. Develop
lower level diagrams as needed.

Figure 06: Sample Level Diagram

Prototype (screen shot)
A prototype is a rudimentary working model of a product or information system, usually built for
demonstration purposes or as part of the development process. A basic version of the system is built,
tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the
complete system can now be developed. Several different platforms may be utilized for the development
of a prototype but this should include the user interface design and the outputs or reports generated by
the system.

CHAPTER IV: CONCLUSIONS AND RECOMMENDATIONS

The Conclusions and Recommendations may be combined or, in long reports, presented in separate sections. If
there are no recommendations to be made as a result of the research, just call this section Conclusions. The
Conclusions section sums up the key points of your research, the essential features of your design, or the significant
outcomes of your investigation. As its function is to round off the story of your project, it should: be written to
relate directly to the aims of the project as stated in the Introduction, indicate the extent to which the aims have
been achieved, summarize the key findings, outcomes or information in your report, acknowledge limitations and
make recommendations for future work (where applicable), and highlight the significance or usefulness of your
work.

BIBLIOGRAPHY

A bibliography is a list of all of the sources you have used (whether referenced or not) in the process of researching
your work. In general, a bibliography should include: the authors' names, the titles of the works, the names and
locations of the companies that published your copies of the sources. Separate resources based from where they
were taken from such as: internet sources, journals, books, conferences, etc. Utilize APA style appropriately, and
arrange alphabetically.

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.
APPENDICES

Appendices contain material that is too detailed to include in the main report, such as long calculations, detailed
technical drawings, tables of raw data, communication letters, interview questions, and photo documentation. The
content should be summarized and referred to at the appropriate point in the body of the report.

DOCUMENT FORMAT

- Short Bond Paper, Font Size 12, Tahoma, Justified

- 1 Inch Margin All Sides, Double Spacing
- Include Page Numbers at the bottom right of each page
- All Section Headings (i.e. Chapter I, Chapter II, …) of the document should be center-aligned in BOLD format
- All sub-headings should be aligned to the left (all underlined sub-headings should be started on a new page)

Property of and for the exclusive use of SLU. Reproduction, storing in a retrieval system, distributing, uploading or posting online, or transmitting in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise of any part of this document, without the prior written permission of SLU, is strictly prohibited.