What You Need to Know about Our Tool:
Our EZ3P Builder is a tool that simplifies the starting of software projects and helps in maintaining the project until closing. It is designed to be used by technical and non-technical Information Technology (IT) professionals. Most software projects go through very similar components and processes where EZ3P Builder has created a tool that cashed on the similarities and best practice and built a component driven system that helps eliminate redundancies and create the basic structure and processes. EZ3P Builder is a component driven system and has the following components:

•	Project Component Tree Setup (User Interview) and Concept
•	Help
•	Documentation
•	Running Projects
•	Change Control Engine
•	Cost Control Engine
•	Reports Engine
•	Existing Project(s)

Project Component Tree Setup (User Interview):
Project Setup or what we call the “Interview” is basically a tree of project components that is needed to start any software project. The questions and fields in the interview are common questions that required by analysts, project managers (PM), architect/designers, developers, stakeholders and other team members. We used best practices and our experiences to reduce the number of questions to essentials ones, set the default values and fill out missing or incomplete information. This helps non-technical users make technical decisions and build the basic structure for starting a software project. EZ3P Builder will reduce both the time and effort of starting a software project by 40%. The documentation, training, frameworks, templates and PM plans and processes help project workers (including the stakeholders) understand the structure that EZ3P Builder creates. The Help and Documentation services provide both the needed help to the interviewees answer questions and fill out the required fields. EZ3P Builder takes interviewees by the hands and goes through the interview suggesting answers and approaches based on best practices and latest technologies.

Component Tree Concept:
We basically took a very complex system and simplified using tree building concept. Our approach is similar to building a tree from a children toy known as LEGO. Our analogy is where the interviewee will build a basic tree with branches. Each branch is also a tree. Once the interviewee finishes building the basic tree; the tree is given to the team, where PM, developers, help disk, testers, analysts and others inherit their branches. They have the option of decorating the branches, adding more branches or trimming them. There are four watch dogs watching over the tree. These are the Calendar, The Assessment, the Change Control and the Cost Control. They are looking for errors, exceptions, conflicts, limits and performance. They send message and reports to each team members to keep them in check. The Calendar is the time watchdog that keeps every team member and processes with the built time frame, otherwise it starts throwing red flags. The Reporting Engine is basically the team photographer who takes pictures of the tree on timely schedule and posts the pictures for the team and stakeholders to see. Key issue here is that each component is an independent prebuilt LEGO that is easy to connect and even easier to disconnect. Each LEGO can also be rebuilt into the needed piece. The LEGO and the interfaces or the connecting parts must be well designed to help speed the connecting, disconnecting as well as reused by other trees.

Help:
Help is primary used by interviewees to trouble shoot certain steps and questions. It shows step by step what is needed and expected values in the Tree Component used by the interviewees.

Documentation:
Documentation covers the theory, technologies, best practices, code examples and current trends. It contains links to other websites. It provides suggestions and recommendations.

Running Projects:
Our system architected each project as a tree of project components and each project tree is an independent tree. EZ3P Builder is also architected to handle more than one project or project trees. Running Project is also EZ3P Builder component that is composed a tree of project trees. Such tree can be used in sharing resources and inheritance. The concept sounds complex, but in reality is more of managing and sharing resources of independent project trees.

Change Control Engine:
System changes must be addressed and controlled using a well-documented procedure. Changes range from simple misspelling of words to major design change with high risks. The Change Control has its own tree and is used to handle the changes and their rippling effect and limitation on what can be changed.

Cost Control Engine:
It has its own tree and uses all other trees and values set in the Procurement to create a budget.

Reports Engine:
The Reports Engine is more a parser that traverses a given tree, collects data and creates reports, graphs and statistics.