Scribd
Upload
158 views12 pages

Embedded System Design - Project Development Phases

The document outlines the 6 phases of a typical project development process: 1) Definition phase to specify requirements, 2) Design phase to develop hardware and software designs, 3) Test definition phase to create test plans, 4) Build and test prototype hardware, 5) System integration and software development phase to integrate and test components, and 6) System test phase to ensure requirements are met. It provides details on activities and goals for each phase such as developing specifications, block diagrams, schematics, software flowcharts, and test procedures. The process is intended to thoroughly plan, design, and test projects to ensure successful and on-budget completion.

Uploaded by

Aravind Balaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
158 views12 pages

Embedded System Design - Project Development Phases

The document outlines the 6 phases of a typical project development process: 1) Definition phase to specify requirements, 2) Design phase to develop hardware and software designs, 3) Test definition phase to create test plans, 4) Build and test prototype hardware, 5) System integration and software development phase to integrate and test components, and 6) System test phase to ensure requirements are met. It provides details on activities and goals for each phase such as developing specifications, block diagrams, schematics, software flowcharts, and test procedures. The process is intended to thoroughly plan, design, and test projects to ensure successful and on-budget completion.

Uploaded by

Aravind Balaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

UNIT – 3

PROJECT DEVELOPMENT
PHASES

Text Book of Reference


Barnett, Cox, &O’Cull “Embedded C Programming and the Atmel AVR”
Thomson Delmar learning 2006
PROJECT DEVELOPMENT PROCESS STEPS
The steps you should follow in the process of developing a project are as follows:

1. Definition phase

2. Design phase

3. Test definition phase

4. Build and test the prototype hardware phase

5. System integration and software development phase

6. System test phase


1. DEFINITION PHASE
This step involves specifying what the device is to do.

in fact, developing a list of specifications that describe the function of the project.

In a commercial environment, providing a formal proposal to go ahead with the project. This step is
sometimes called the feasibility study.

The purpose of the research conducted during the definition phase is to ensure that the project can, in
fact, be accomplished.

The early portion of this research will result in a block diagram; an example is shown in Figure. This
block diagram will show, in somewhat general terms, the circuits that will make up the final project.

Sensor Block Microcontroller Display Module


1. DEFINITION PHASE
At the end of the definition phase, a complete set of specifications for the project is
developed.

These include electrical specifications as well operating specifications that detail the
operation and human interface to the project.

In a commercial environment, a Project Proposal is written to summarize the definition phase


of the project.

In addition to summarizing the research and feasibility testing and providing a written list of
the project specifications, the proposal will include an anticipated budget for the project and
a schedule for completion of the project. The purpose of this proposal is to give the customer
(or upper management) confidence that investing money in this project will result in a
successful outcome.

The definition phase is a relatively short but very critical step that consumes approximately
10 to 15 percent of the total project time.
1. DEFINITION PHASE

Project Title

A. Description of project

B. Summary of Research

C. Block Diagram

D. Project Budget

E. Project Schedule

F. Appendix
2. DESIGN PHASE
• The major goal of the design phase of the project is to fill in the functional blocks developed during
the definition phase with actual circuitry and to plan out, in flowchart form, the project software.

• The hardware design and the software plan must be accomplished concurrently.

• This step will consume 40 to 50 percent of the total project time.

• The following two characteristics seem to reflect the approach of many engineers to the definition
phase of the project:

• Designing the project determines the success of the project, both in terms of function and efficient
development—for efficient, read “on time and under budget.”
2. DESIGN PHASE

Software development steps:

1. List the tasks to be completed by the software.

2. Prioritize the tasks and determine which are critical and will need to be handled on an interrupt
basis and which are less critical.

3. Create a software for each interrupt function.

4. Create a program code to complete the project’s entire task.

When the project has been thoroughly designed, you will have a detailed block diagram
(showing all blocks and signals), a complete set of schematics, and a set of software outlines.
3. TEST DEFINITION PHASE

• The test definition phase of the project has the goal of ensuring that the project meets all
of its specifications and goals through the development of a test specification for the
project.

The test specification is divided into two parts:


1) Intermediate tests
2) Final tests or System tests

• The intermediate test specification is a list of functional tests to be performed on each


block or group of blocks in the project.

• The final test specification is a document that includes all of the test procedures which
will be used to verify that the project prototype meets all of its intended specifications.
4. BUILD AND TEST THE PROTOTYPE HARDWARE PHASE

 In this step, you should construct and thoroughly test the hardware for the prototype
project.

 Use the actual input and output devices for testing wherever possible.

 Signal simulators can be used during system integration and software development.

 After this step, you should be absolutely sure that the correct input signals are being
applied to the microcontroller from each sensor and that the correct output signals from
the microcontroller will drive the output circuitry in the expected manner.
5. SYSTEM INTEGRATION AND SOFTWARE DEVELOPMENT PHASE

 This step is the software outcome to the hardware step above.

 Writing and testing the software means to develop and individually test each of the
functions when you designed the project.

 Use a simple main() function to use each of the individual input device functions and
output device functions. so that, you can ensure that each of the individual input and
output functions works correctly.

 The goal of this step in the process is to have a fully working project using the real or
simulated inputs and outputs
6. SYSTEM TEST PHASE
 The system test is the activity that actually puts the project into use.

 During the system test phase, the project should be tested in accordance with the final
test specification developed earlier to ensure that all of the specifications defined in the
definition phase of the process are met.

 For a commercial project, the system test phase will also include a demonstration for the
customer, and it will often include transfer of the intellectual property (IP) relating to the
project.

 The IP includes complete documentation and records relating to the project, and it may
be the property of the customer, depending on contract and business stipulations
PROJECT DEVELOPMENT PROCESS SUMMARY

You might also like