UNIT 2. PROJECT PLANNING. SUBMISSION OF DOCUMENTATION.

Project planning.

2.1. Introduction.
2.2. Phase of the project's feasibility study.
2.2.1. Analysis of the current situation.
2.2.2. Feasibility study.
2.2.3. Alternatives and solution selection.
2.2.4. System requirements for the proposal.
2.2.5. Project plan. Gantt and Pert diagrams.
2.2.6. Study of the budget.
2.2.7. Risk assessment (if applicable).
2.3. Relationship of the project with the professional modules of the cycle.

2.4. Project planning and analysis phase.

2.4.1. Project typology.
2.4.2. Review of initial forecasts
2.5. Execution and development phase of the project.
2.5.1. Detailed analysis.
2.5.2. Physical design.
2.5.3. Logical Design.
2.5.4. Review of the analysis forecasts.
2.5.5. Difficulties encountered in its development.
2.6. Bibliography.
2.7. Developed index phase project planning (possible index).

1
2.1. INTRODUCTION TO PROJECT PLANNING.

A project is the planning of a set of sequenced or simultaneous activities that involves people.
hardware, software and communication components aimed at achieving desirable results in a
information system.

In this phase, all the activities that make up the project and the relationships between them are determined.
indicating what must be done, when it should be done, that is, when they start and when they end
activities and who should carry them out with the designated resources for it

The requirements are determined, that is, what we need or what needs the client has.
who the project is aimed at and how it will develop over time. The required needs are met for
keep the project under control and ensure its development.
The restrictions on available resources (spaces, hardware, software, and personnel) are established.
adapting them to the time planning and the cost it will entail for us.
The set of tasks and activities is established that entails the execution of the project itself, it is carried out to
I finish the execution of these, responding to the specific characteristics of the project, managing the
resources adequately for your development.

The scope of the project is studied:

As activities, meetings are held with the client (if any) to establish what they want and when they want it.
start-up. Meetings are planned with technical staff to describe the production process
current and the changes to be made until having a clear vision of what the client wants and the parts of the system
that will be affected.

For the development of a personal project, it is specified what is desired to be done and the time it will take.
put it into operation. The necessary resources are established to achieve it at both hardware, software, site, and levels.
of people. Activities are set to achieve the established objectives by sequencing them over time.

As an output document, a report is obtained with the needs of the client (or of our project), the
project completion date, a list of components that will be affected and the quantity, all the
important information regarding changes to be introduced in the production system and its operation.

2
2.2. PHASE OF THE PROJECT FEASIBILITY STUDY.

It is the initial phase of any project and the objective is to analyze whether the development of the project itself (or of the company) ...
should or should not take place, as it may happen that on certain occasions the implementation of this may have
more problems than benefits when carrying out a project.

Describe the type of project, the objectives to be achieved are indicated classified by type of objective.
the references used are specified, a list of specific terms and acronyms is created, and it is also established
What is the interest of the project and who is it aimed at?
The feasibility analysis must include at least the following activities:
Creation of the tracking record in the management tool used.
Preliminary analysis of the project scope.
Analysis of project execution risks.
Feasibility analysis according to deadlines, cost, and quality.

If the feasibility analysis is positive, that is, there are no initial reasons not to undertake the project,
We can move on to the planning and analysis phase of this. The feasibility analysis allows us to analyze
fundamentally the aspects of economic viability, technical viability, and organizational viability.

activities
Detailed economic studies of the project (own or of the company) are carried out at the economic level.
checking if there is money available, the company's solvency, regarding possible acquisitions to be carried out
cable for the implementation of the project, spaces, equipment, communications, etc.

At the level of organizational modification to be developed during the project, it is determined whether they are manageable by
we (own project) or by the client and in the desired time, basically if new staff is needed or
simply relocate the existing ones.

At the level of user/employee training, it is established whether it is viable to assume the changes and the subsequent
operation of the computer system. This information allows us to generate the necessary reports that we
They will serve as a basis for making the decision along with the input documentation.

Determined to continue with the project, an estimation of the necessary resources and time needed is carried out.
to carry out the project by presenting it (to the client) as a budget. If it is accepted (by the client), then
a pre-contract for work will be drafted and signed by the responsible party of both sides (Note: In case of dismissing the
A justification document is created with a report.
The document with the acceptance proposal or budget (or rejection - not our case -) is obtained.

2.2.1. Study of the current situation

Starting from the work context and the way of carrying out the process, the system is physically described.
indicate whether it is a new project or if there is an existing system that is desired to be changed, following legal regulations.

There are systems that start from scratch with a nonexistent system, from an already existing system and that
wish to update, change certain parts or change it entirely; in all cases it must be indicated the
starting situation and the situation that is desired to be achieved, keeping in mind in the case of an existing system
what is desired to be kept or reused and what is desired to be changed.

3
 2.2.2.- Feasibility study

In our own project, we must first consider whether we have the time to carry it out.
maintain it and improve it if necessary and have enough money to acquire the necessary resources to
its development.
When it comes to a project for a client or company, we must obtain economic information from the
company to determine if it has sufficient capital to develop the project.
• Technical viability. The monthly monetary needs for system maintenance are estimated in € if
hire staff and/or what the payment for the development will cost. The review of the contracts for the staff, their
qualifications indicate the possibility of using computer tools to manage their work.
• Economic viability. The current accounting, investment capacity of the company in euros (€) is studied.
annual, this capacity will indicate the economic viability of the project. It also deals with whether it is necessary to
acquisition of equipment, network infrastructure, operating systems, and applications in money (€).
• Organizational viability. The available spaces are analyzed (owned, rented, or company-owned), whether there are
need to rent a new premises, whether extensions of the existing spaces are necessary or if it is enough
with a reorganization if we have them.

2.2.3. Alternatives and selection of the solution.

Based on our idea that we have for the development of our system, other things are established.
feasible alternatives for obtaining the solution and the justification for why they are discarded in favor of the
chosen option establishing the conclusions.
The advantages or benefits and the drawbacks of the system are established.
When proposing different solutions for our system, we must establish a set of parameters.
mainly documenting:
Brief description of possible solutions.
Economic study or analysis: hardware/software components, prices, people involved, etc.
Brief feasibility study of those possible solutions.
Regarding the chosen solution, basically the following will be done:
Justification of that solution.
Diagram or scheme with the new organizational structure of hardware/software resources.
Technical documentation.
Applicable regulations on safety, types of licenses, intellectual property, etc.

4
2.2.4. System requirements for the proposal.

The system requirements and constraints are established and classified according to their priority.
The requirements or prerequisites allow to establish in an objective and concise way what is going to be done.
system to be developed, helping to establish specific objectives that must be met to achieve development
a system that meets the functionalities specified initially.
Requirements can be technical such as the hardware to be used, data control, and their relationships.
the functional requirements of the system operation.

2.2.5. Project plan. Gantt and PERT diagrams.

With the available resources, the project tasks are established and scheduled over time. Once completed,
The feasibility study creates the general project plan in which the different phases to be carried out are specified.
and the time we expect to use. At the end of the detailed analysis of the following phase, the project is refined.
expressing new needs or requirements for development, indicating all the steps to be taken and
dividing it into simpler subprocesses to implement the system.
Now a realistic estimation of the time for each phase is made. This plan will be delivered to the client and
remembering that these are only approximations and the times will be finalized later. It is important to make very clear
I made it clear to the client that there are still several weeks to know the actual time distribution and that it could vary.

Gantt charts. It is a tool that allows the user to model the planning of tasks for the
implementation of a project through a graphical representation, used by the project manager to
to know their progress, and for the people involved in it as a means of communication.
Gantt chart design tools are used for the creation and visualization of reports: Day
(free), GanttProject (free), Openproj, TaskJuggler, Microsoft Project, Planner, etc.

5
 Pert diagrams. Technique to optimize the development and execution of a complex project through the
preliminary analysis of all the activities or tasks that compose it and that are temporally related.

2.2.6. Budget study.

Cost estimates for materials, personnel, and economic factors are made, analyzing the cost and the
benefits that would arise from the implementation of the system.
We create the budget and the pre-contract since we understand that the project is viable and we present it for your approval.
signature and acceptance (by the client). The contract is signed at the end of this phase and all documentation is presented with
new time estimates if necessary and with the project plan along with the contract for signing.

Table: Proposed overall budget (refine in a more detailed manner) in Euros.

No. Concept Quantity Price Total
1. Personal 3 €6,200 18,600 €
2. Staff training 3 1,500 € 4,500 €
3. Hiring of personnel 1 500 € 500 €
4. Acquisition of hardware. 4,500 €
5. Acquisition of software and licenses. 1,500 €
6. Installation of hardware and wiring. 900 €
7. Software development. 2 1,500 € 3,000 €
8. Acquisition/rental of the facilities 12 months 450 € 5,400 €
9. Acquisition of materials and furniture. €3,000
10. Maintenance 300 €
42,200 €

2.2.7. Risk assessment (if applicable)

Planned the project's scope, timeline, budget, tasks, and project achievements,
They plan in advance for unexpected actions and assess the possible future risks that may affect the project.
In general. A list of potential risks is established, classified, and a contingency plan is set up.
In the case of projects such as prototypes, etc. Some risks that can affect a project are:
Economic planning. Capital is available or there may be additional costs.
Technological. The best tools are available or they may become obsolete.
Legal. The legal order is fulfilled or surpassed.
6
2.3. RELATION OF THE PROJECT WITH THE PROFESSIONAL MODULES OF THE CYCLE.

The contents of this module relate to all the general objectives of the cycle and must be
based on professional, personal, and social competencies and on professional qualifications
competency units of the National Catalog of Professional Qualifications included in the title. (Real
Decree 1629/2009, of October 30.

The integrated ASIR project complements the established training of the other professional modules that
they integrate the title into the functions of context analysis, project design, and execution organization.
The activities to be developed must be related to at least 4 of the modules taught during the
development of the training cycle, that is, the aspects to be addressed in the project of each
module involved that affects the development of this.

The modules that will cover the content are:

Implementation of Operating Systems.
Operating Systems Administration.
Network Planning and Administration.
Network and Internet Services.
Hardware fundamentals.
Database Management.
Management of Database Management Systems.
Markup Languages and Information Management Systems.
Web Application Deployment.
Security and High Availability.
Job Training and Orientation.
Company and Entrepreneurial Initiative.

The project idea initially stems from the development of some of the contents of a module, which
subsequently they are expanded to cover other aspects of the project and thus manage to address other contents of the
cycle seen in other modules, recalling that a project must involve the application of knowledge
acquired in several of the completed modules and carry out research tasks by the students of
new technologies used in the current market.

7
2.4 - PROJECT PLANNING AND ANALYSIS PHASE.

The objective is to define in as much detail as possible the tasks to be carried out and the necessary resources to carry out.
Good end to the project. A miscalculation in this phase can have negative effects on its development.

To define or delimit the project, we need to take into account:

It is established and analyzed what we want to achieve.
The size of the application to be developed is estimated, or if an already implemented system is studied.
The tasks to be performed are identified by assigning resources to each of the tasks.
A schedule for each task is established.
The economic study is conducted.
The key activities at this stage are:
Project scope analysis.
Estimation of effort, costs, and resources.
Definition of the project plan.
Negotiation of the contract (if applicable).
The most common resources in the development of an IT project are ICT components such as they can be
be the hardware, the software, and the communications.
If the project is finally viable and receives the green light, it is formalized in a contract that includes all the
terms of the agreement.

2.4.1.- Typology of projects.

To see those resources, we must take into account the type of software project to be developed:
Hardware project. We are working on the components that will be used, the operating system on which
that will be carried out, the basic applications for its operation and the services that will be offered.
Software project. The methodology to be followed is established, the tools that will be used, the
techniques used for the development of the computer application.
Communications and networking project. Protocols, the system and location of the wiring are studied.
interconnection devices, the technology that will be used (mobile devices, server/s, equipment).
Operating system administration. Users, resources, service deployment, scalability, etc.
Audits. Security systems, quality study, applicable legislation, etc.
Virtualization. Servers, networks, and work environment are virtualized.
Computer security. The protection of systems both proactively and reactively, security of the
information, backups, etc.
Web development. The technologies to be used are established (markup language, presentation, programming language.
server and client script), server to host the service, DBMS, security in the service, etc.
Innovation. Creation of a new service and technology used, modification of an existing service and its
scope of application, etc.

2.4.2.- Review of the initial forecasts.

Since the project is already in full development and all the tasks to be carried out are known with their
requirements and constraints, the time to carry it out, the budget and the risks to be considered are reviewed
The initial forecasts assign resources to each of the tasks, establishing a new schedule.
the tasks and a new budget or economic study with the new requirements is to be done again
incorporated.

8
2.5 - EXECUTION AND DEVELOPMENT PHASE OF THE PROJECT.

In the execution phase of project management, we ask ourselves how to carry it out, the problems that arise.
they usually find the most cost-effective solution considering factors such as efficiency, economy and
restrictions that we have indicated earlier. What is established in the project planning is carried out.

The main activities of this stage are:

Setting up the work environment.
Assignment of planned tasks to available resources.
Execution of the planned tasks.
Management of change requests.

In addition, in this phase, a follow-up and control of the project is carried out to ensure compliance with the
planning and the quality of the work done, to detect deviations before they become a
problem for the project's success.

The goal is to create the complete Information System on paper. It starts by analyzing the functional specification.
expanding the document (top-down design) to the highest level of detail specifying inputs and outputs
of data, the modifications of them, the relationships between the different elements, etc.

With the system described in its entirety (optionally to represent it graphically, you can use)
UML diagrams, DFDs, graphs, etc.) we move on to creating the system hardware design, the equipment and its
connections, their distribution, etc. Then the main software and the rest of the necessary software are defined,
permissions and special configurations, etc. This documentation is used as a basis for the next phase.

2.5.1.- Detailed analysis.

It is part of the operation of the system and the project plan of the Initial phase, moving on to be developed the
activities of this stage.

The activities are developed through the top-down approach until the last one is determined.
level through an iterative process. In each step we will ensure that the descriptions we create meet
the needs of the client and ensure the viability of the project.

Add a description of the data to the documentation, in which we relate for a simple process and
Indivisible the necessary data, the origin of these, the processes they undergo, and their destination. If they are used
interfaces and if necessary, a description is included with the data entry screen, some algorithm
mainly about the data, report structure, etc. Ultimately, it represents what the user will see, like
makes use of it, making estimates of data usage, especially regarding the amount of
transferred information and the frequency with which it is carried out, for example, a description of a delivery note.

As an output, the external specification is obtained (the product is specified considering its interface and the
user interactions) and the documentation generated at this point.

9
2.5.2.- Physical design or hardware of the system

The activities are carried out by reviewing the external specification (interfaces and user interaction), such as the
data inputs and outputs, the higher level descriptions to estimate processing capabilities
in the transfer teams in the networks.
The optimal physical structure for the system is determined, taking into account whether a system will be used.
integrated or external (to our system or that of the company).
The network is designed using security in transfers, in access, and in maintenance of the
Data. Access to the system must always be ensured to prevent its operation from being paralyzed.
The teams and their capabilities are defined, the servers and their locations, the communication system,
the security and access mechanisms to the service.
Once the design is finalized, the current hardware is checked to indicate which will be reused and where to acquire new ones.
teams, creating a hardware purchase document to be presented to the client for approval.

As a result, the physical design and hardware purchase proposal are obtained.

2.5.3.- Logical design or software of the system.

So far, the processes and data have been identified, now the software to be installed, the areas or
departments that exist and their structure, users and organization of users to implement security in
the access and management of data. The reports that the system already incorporates and those that do not are checked.
they can generate them and we will have to create them ourselves later.

The activities focus on the design of the system based on the main software and we determine the rest of the
software involved in the system: client and server operating systems, application software and the rest
of the software we need (or from the company).

Before generating documentation, we should review the installed software and see if it can be partially reused.
With all the data, we create two output documents:
The logical design that will gather the necessary software and its configuration
The software purchase proposal that we will present (to the client) for their acceptance.

10
2.5.4.- Review of the analysis forecasts.

Starting from the Project Plan, the Project Plan is reviewed to determine if the objectives have been met.
temporary, determining whether the forecasts made in the previous phase were accurate. In case that
noting deviations will modify the plan and notify the client.

Here, each phase of the project plan is divided into subprocesses that represent a unique and specific task.
to keep an exact control of time. Thus, the physical design is divided, for example, into component analysis.
current, database management system design, etc. The time is modified, changing from indicating dates
relative to exact dates with a one-day separation.

This forecast document must be ratified by us (the client), accepting the new timeframe.
and indicating that it is a realistic forecast, but that deviations may occur due to external reasons.

The Revised Project Plan is obtained as an output document.

Figure: Summary diagram of the development phase.

2.5.5.- Difficulties encountered in its development.

Some factors that affect the development of a project and that are often overlooked:
It involves resource expenditure (cost and time)
Resistance to additional work
Lack of resources
Lack of training
Lack of spirit
Increase in bureaucracy

11
2.6. BIBLIOGRAPHY.

Good practices in the management and direction of IT projects. National Technological University.

[Link]

2.7. POSSIBLE INDEX OF THE PROJECT PLANNING PHASE.

1.- Introduction.

2.- Phase of the project's feasibility study.

Introduction to feasibility.
2. Study of the current situation.
3. System Requirements.
4. Alternatives and solution selection.
5. Project Plan
6. Budget
7. Risk assessment.
3.- Relationship of the project with the professional modules.

4.- Project planning and analysis phase.

1. Introduction to project planning.
2. Functional requirements of users and system operation.
3. Non-functional requirements.
4. System diagrams.
5. Logical data diagrams.
6. Conclusion of the analysis.

5.- Execution and development phase of the project

1. Introduction
1.1. Selection of the network architecture
1.2. Selection of the database management system
1.3. Selection of the server(s) to be used: web, ftp, etc.
2. Platform configuration.
3. Layers of the application
4. Database structure
5. Network system architecture

6.- Final conclusions.

2.1 Final Conclusions.
2.2 Temporary deviations.
2.3 Possible extensions and modifications.
2.4 Personal Assessment.
12