The document discusses the requirements for a project that involves analyzing the layout and effectiveness of websites for different product types based on 10 essential elements of an effective website. It provides 4 questions to evaluate the overall effectiveness of the websites visited, requiring a minimum 2-page double-spaced response referencing additional sources in APA style.

1. According to an article published in Forbes in 2010, the 10
essentials of an effective website includes the following:
company/product easily identifiable, front and center contact
information, fast search bar, speed; detailed, well-organized
content; product qualities highlighted, differentiated benefits
presented, encourages return visit, easy to navigate, and fresh
new content.
Visit two-three websites for ONE type of product (e.g., laptops,
laundry detergents, beverages, athletic shoes, etc.) and analyze
the layout of these sites including the 10 essential elements
listed above. Respond to the following questions evaluating the
overall effectiveness of the websites.
1. How does a consumer’s perception affect the influence the
website has on the consumer? Include a discussion of the
sensory aspects.
2. What are the stages of perception as it relates to consumer
decision and buying? Relate these stages to the qualities of
effective websites as identified by Forbes.
3. How does a consumer’s personality affect his or her buying
decisions which inevitably shapes his or her lifestyles? Include
a discussion of how a consumer’s view of him or herself also
impacts buying decisions.
4. Analyze the effectiveness of the websites in reaching their
respective target markets. What specific things would you
recommend implementing in order to improve upon the
effectiveness?
Your response should be a minimum of two pages, double-
spaced. References should include your textbook plus a
minimum of one additional credible reference. All sources used,
including the textbook, must be referenced; paraphrased and
quoted material must have accompanying citations, and cited

2. per APA guidelines.
Title of the Project
by
Student Name
This is an Engineering project submitted to the Gannon
University graduate faculty in
partial fulfillment for the degree Master of Science in
Engineering.
Major Subject: Electrical Engineering
Approved:
Advising Professor in Charge of Major Work
Chairperson of Major Department
Gannon University
Erie, Pennsylvania 16541
Month, Year
Acknowledgements
The writer thanks mentors, colleagues, lists the individuals or
institutions that supported the research, and gives credit to

3. works cited in the text for which permission to reproduce has be
granted. ACKNOWLEDGMENTS appears centered at the top of
the page.
Abstract
Give a 60-100 word abstract/executive summary of the project
here.The abstract briefly summarizes the thesis and the contents
of the paper. ABSTRACT appears centered at the top of the
page.
Table of Contents
51.
INTRODUCTION
1.1
Scope
6
1.2
Background
6
1.3
Summary
6
1.4
Road Map to the report
6
2.
REQUIREMENTS ANALYSIS
7
2.1
System Overview
7
2.2
Application Constraints and Dependencies

4. 7
2.3
Specific Requirements
7
2.4
Interfaces
7
2.5
Summary
8
SYSTEM DESIGN
9
3.1
Top Level Design
9
3.2
Product Flow
9
Interface
9
3.4
Description
9
3.5
Initialization
10
3.6
Interface Design
10
3.7
Functional Design
11
3.8
Summary
11
4.

5. FUNCTIONAL TESTING
12
4.1
Interface Functionality Test
12
4.2
XYZ Functionality Test
12
4.3
Summary
12
5.
SYSTEM INTEGRATION AND VALIDATION
13
5.1
General Assumptions
13
5.2
Helpful Information
13
5.3
Test Facilities
13
5.4
Special Equipment
13
5.5
Test Procedure
13
5.6
Overall Test Summary
13
5.7
Summary
13
6.

6. CONCLUSIONS AND RECOMMENDATIONS
14
7.
REFERENCES
14
8.
APPENDIX
14
A Quality Functional Deployment (QFD)
14
B Sample Format of Output
14
C Data Dictionary for Key Terms
14
D Screen Snapshots (if applicable)
14
E Failure Mode and Effect Analysis (FMEA)
14
List of Symbols
AC
: Alternating Current
FTR
: Formal Technical Review
GE
: General Electric
GETS
: General Electric Transportation Systems

7. GUI
: Graphical user interface
Mph
: Unit of speed in miles per hour
List of Figures
3Figure 1: Top-Level Interface Diagram
Figure 2: Top-Level Structure Description
3
Figure 3: State Machine
5
List of TABLES
6Table 1. XYZ Test Results
Table 2. Test Procedure 365
7
Table 3. Test Summary
7
INTRODUCTION
Introduce the project succinctly. Chapter 1 is usually the
introduction. Sections should include the objectives of the
project, the design criteria, the constraints, and the background
material leading up to the current project.
NOTE: Your goal is to communicate your work in writing: in a
clear, well-structured, readable manner. E.g., the chapter titles
are only strongly suggested. Please adapt them as is appropriate.

8. If they are not applicable to your project, rename them. Add
chapters as necessary. Please work with your advisor to
develop an appropriate organization for your report.
1.1 Scope
Define scope of the problem clearly.
1.2 Background
Any background information, breakdown of the project. This is
often a description of the environment in which the problem
occurs.
1.3 Summary
Summary for the section, mentioning the objective clearly.
1.4 Road Map to the report
Section 2: Requirements Analysis: Requirement elicitation from
the customers.
Section 3: Design: Major design decisions and constraints
Section 4: Testing: Functional testing procedure and results
Section 5: Integration: System level integration and validation.
Section 6: Conclusions and Future recommendations.
Section 7: References to related documents.
Section 8: Appendices.
2. REQUIREMENTS ANALYSIS
This section defines the requirements for the project. Mention
all requirements elicitation or design tools, if any (e.g., six
sigma tools) used in the requirements process and the validation
(reviews) process. Review results are appropriate to include in
the discussion.

9. Chapters 2 & 3 should focus on the analysis and design process.
These should be described in detail along with the resulting
design obtained. Design considerations and tradeoffs should be
discussed in detail. All illustrations and/or figures shall have
descriptive labels and be discussed in the text. If only a few
figures are used, they shall be included in the text (typical).
Otherwise they shall be given at the end of the chapter. These
may be merged into one chapter, as appropriate.
2.1 System Overview
Define the system from the requirements perspective. It is
typically appropriate to indicate the key problem to be solved
and the benefits (e.g., business-value) provided by the system.
2.2 Application Constraints and Dependencies
Any constraints or/and dependencies are discussed in this
section.
2.3 Specific Requirements
This section tells about the specific requirements (typically
feature level) involved in the project. These should not be
written as a requirements specification. Your goal is to
communicate to an unfamiliar reader what the specific
requirements are, and how they relate to one another.
Be sure to provide the context for more detailed descriptions of
the requirements for subsequent sub-sections. Use-case
diagrams may be appropriate here.
.
2.3.1. Functional Requirements
Functional breakdown of the requirements. These sub-sections

10. should describe in more detail the feature-level requirements
mentioned above. Please note that continuity between
subsections is an important communication goal.
2.4 Interfaces
Interface is another key area need to be examined specifically.
All the interfaces should be clearly specified under this section.
Use-case diagrams may be appropriate here. Your goal is to
communicate why each interface is necessary, and what each
interface must support.
2.4.1. User Interface
If applicable… Note that continuity among sub-sections is
important.
2.4.2. Other Interfaces
As applicable.
2.5 Summary
Summarize the requirements analysis and refer any documents
for further details.
3. SYSTEM DESIGN
This section covers the design process involved in the
development of the product. Mention key decisions and the
review process and if any key points in the review minutes.
Throughout this chapter, it is appropriate to include diagrams
(such as class diagrams, functional-flow block diagrams,
deployment diagrams, schematics or other diagrams that
indicate the organization of the design and to use interaction,

11. statechart or other types of diagrams to indicate the behavior of
the design.
Review results are appropriate to include in the discussion.
3.1 Top Level Design
In this section, discuss the top level design for the product. It is
best if the organization of the design is described in the context
of the requirements previously described.
3.2 Product Flow
If applicable, define the flow of the activities.
3.3 Interface
Inputs and outputs of the system, use diagrams as helping tools.
Figure 1: Top-Level Interface Diagram
3.4 Description
The design is divided into five sub sections [Figure 2]:
Figure 2: Top-Level Structure Description
Pseudocode
If applicable.
3.5 Initialization
This section defines the initialization phase of the project. Pre
requisites etc…
Interface

12. Define the interface of the things separately. Use diagrams.
Pseudocode
3.6 Interface Design
Interface
Input:
Output:
Other calls:
Description
3.6.1. XYZ Function
Describe the functionality of every function separately.
Interface
Input:
Output:
Pseudocode
3.7 Functional Design
Functional design description dictates the functionality of the
product. Functions discussed in this section directly define the
working of the product.
3.7.1. XYZ Function
Interface

13. Pre-condition:
Output:
Other calls:
Pseudocode
Figure 3: State Machine
3.8 Summary
Give the summary of the design process. Review results and any
references.
4. FUNCTIONAL TESTING
Functional testing is an integral part of the development
process. This section covers the testing of the key requirements
from the Requirements phase (See Section 2) as independent
sub-systems using a black box testing approach.
The test procedure and the test results should be presented and
discussed in detail.
4.1 Interface Functionality Test
Purpose:
Procedure:
Test Results:
4.2 XYZ Functionality Test
Table 1. XYZ Test Results

14. XYZ
Expected Result
Actual Result
Remark
4.3 Summary
Summarize the test results, refer to test plan for further details.
Discuss any interesting results.
5. SYSTEM INTEGRATION AND VALIDATION
System level testing is necessary for validating the system
integration process. The product was tested at the modular
level, but it should also be tested along with other related
systems.
5.1 General Assumptions
5.2 Helpful Information
5.3 Test Facilities
5.4 Special Equipment
5.5 Test Procedure
Table 2. Test Procedure 365

15. Action
Expected Result
Pass / Fail
Test Result:
5.6 Overall Test Summary
Table est Summary Matrix
Table 3. Test Summary
Overall Test Summary
Test Engineers:
Date: February 2000
R/N :
Test1
Passed
Test2
Passed
Test3
Failed, Repeated/Passed5.7 Summary
Give the summary of the system validation and results.
1. CONCLUSIONS AND RECOMMENDATIONS
Give the conclusion and success/fail and any other comments
about the product.

16. Discuss future benefits and further application in other areas.
The conclusions should be stated for the project. These should
be short and to the point. The conclusions must be supported by
the material in the previous sections.
6. REFERENCES
The reference list is the last part of the paper and before the
appendices. The references are listed in the order they are first
referenced in the text.
Example reference:
[1] Hazen, Samuel L. “A Major Breakthrough in Optimal
Control Theory,” J. of Applied Control Theory, Vol. 3 No. 1,
New York: Wiley Publishers, 1990, pp. 23-69.
[2] GETS System Design Specification for Propulsion Power
Control 84A201047 Rev. N
[3] Public, Fredrick Q., The Race to Space, Rockets-R-Us Press,
Cape Canaveral, FL, 1963, pp. 231-242.
7. APPENDIX
An appendix contains material related to the text but not
suitable for inclusion in it. An appendix is a group of related
items. All appendices go at the end of the paper, not at the end
of a chapter. All appendices shall be referenced in the text.
A Quality Functional Deployment (QFD)
B Sample Format of Output
C Data Dictionary for Key Terms
D Screen Snapshots (if applicable)
E Failure Mode and Effect Analysis (FMEA)
1 inch

17. General Guidelines:
All texts shall be placed within the specified margins.
No one-sentence paragraph.
No one-paragraph section.
Figure captions are placed below the figures.
Table captions are placed above the tables.
Figures or tables shall be placed right after the text to which
they are referred as much as possible.
Line spacing and font sizes should follow this sample document.
If other font sizes is chosen, please bear in mind that the font
sizes and line spacing selected should give the reader maximum
comfort in reading without scarifying the professional
impression of the text layout.
1 inch

18. 1 inch
1 1/4 inch
Give enough spacing.
System to be Implemented
User Options
Data from somwhere
Statistical data
Download Status
Global variables:
All global scope variables.

19. Initialization:
Initial settings,
Interface:
Xyz interface
Abc interface
Functionality:
Function 1
Function 2
Communication Functions:
If applicable

20. Define the details of the initialization phase.
Help function,
Display function
Function1()
Function 2()
State 1:
State 2:
State 3:
Start

21. Condition1
Condition2
Condition3
Condition5
Condtition4; Stop
Enough Spacing !!!
8
1