< Give a brief summary (100-200 words) of the key information presented in the document. Do not simply describe what each segment of the writing offers, but condense the significant aspect of each section into the key facts and primary end states, decisions made, or conclusions reached in each section. Succinctly state the aspects of what situation was addressed by the research, why was the situation significant to its stakeholder, what solution design was followed, what final development arose, what major difficulties were addressed, how successful was the research in achieving its goals.>
<Provide a short description of the software, system, process, or product – henceforth referred to as “product” — beingbuilt or enhancedby the technical directed project report (TeDPR). Describe its purpose, including relevant benefits, objectives, and goals. Relate the system to corporate goals or business strategies. This section is a relatively high-level, brief description.>
<Put the product in perspective to other related products and the user’s environment. If the product is independent and totally self-contained, state so. If the product is a component of a larger system, this subsection should relate how these systems interact and should identify the relevant interfaces among the systems. Provide a context diagram here. >
.3 Summary of Capabilities
<Summarize the major benefits and features the product provides. Organize and state the features so that the list is understandable to individuals initially becoming familiar with the product.
A simple table listing benefits and features may be sufficient. Justify the contents of the cells to “flush left”.>
|(benefit 1)||(feature 1)|
|(benefit 2)||(feature 2)|
|(benefit 3)||(feature 3)|
|<list may continue>|
<Identify alternatives perceived as available. These options can include buying a competitor’s product, building a homegrown solution, or simply maintaining the status quo. List any known competitive choices. List the major strengths and weaknesses of each option. State how the developed product compares. >
<Describe how you approached the development of the project. Explain difficulties you faced in any phase of the development. Discuss which aspects of the project management phases – problem identification, analysis, design, verification, or deployment — were particularly challenging, why, and how did you address the challenges.>
<This section provides an overview of the entire design document. This document describes all data, architectural, interface and component-level design for the software. Explain how the design decisions offered interesting or challenging consideration by you.>
<Overall goals and software objectives are described.>
<A description of the software scope is presented. Major inputs, processing functionality, and outputs are described without regard to implementation detail. Supporting diagrams appropriate for inclusion.>
<The software is placed in a business or product line context. Strategic issues relevant to context are discussed. The intent is for the reader to understand the ‘big picture’.>
<Any business or product line constraints that will impact he manner in which the software is to be specified, designed, implemented or tested are noted here.>
<A description of all data structures including internal, global, and temporary data structures.>
<Data structures that are passed among components of the software are described.>
<Data structures that are available to major portions of the architecture are described.>
<Files created for interim use are described.>
<Database(s) created as part of the application is(are) described. Include an ERD with structural rules governing its relationships and organization. Relational schema included in appendix. Major, unique, data definition challenges described here.>
<A description of the program architecture is presented.>
<A detailed description the program structure chosen for the application is presented.
188.8.131.52 Architecture diagram
A pictorial representation of the architecture is presented.
<A detailed description of key software components contained within the architecture is presented. The section is repeated for each of n components.>
184.108.40.206 Processing Narrative for <component name>
<Replace the <component name> in the title with the name of the component in the system. Provide a processing narrative for the component. Describe its role in the system.>
<Continue adding individual “Processing Narrative” sections for each key software component.>
<Address the following points in a degree appropriate to your project.>
- Component n interface description.
A detailed description of the input and output interfaces for the component is presented.
- Sub-Component n.m processing detail
A detailed algorithmic description for each sub-component within the component n is presented.
Repeat section; describe for each of the m sub-components of component n.
Optionally, choose to add the following elements, also.
- Interface description: A description of sub-component m inputs and outputs is presented.
- Algorithmic model: The pseudocode listing for sub-component m is presented.
- Restrictions/limitations: The external environment and/or infrastructure that must exist for sub-component m to operate correctly is provided.
- Local data structures: The data structures used within sub-component m are presented.
- Performance issues: Information on topics that may affect the run-time performance, security, or computational accuracy of this sub-component are presented.
- Design constraints: Attributes of the overall software design (including data structures, OS features, I/O, and interoperable systems) that constrain the design of this sub-component are presented.>
- External machine interfaces
Interfaces to other machines (computers or devices) are described.
- External system interfaces
Interfaces to other systems, products, or networks are described.>
<A description of the user interface design of the software is presented. In the following sections>
<A detailed description of user interface including screen images or prototype is presented.
220.127.116.11 Screen images
<Discussion of the interface from the user’s point of view.>
18.104.22.168 Objects and actions
<All screen objects and actions are identified.>
<Conventions and standards used for designing/implementing the user interface are stated.>
<GUI components available for implementation are noted.>
<The user interface development system is described.>
<Special design issues which impact the design or implementation of the software are noted here.>
<Summarize the software items (programs, modules, classes) and software features tested. The need for each item and its version/revision history may be included. Also specify characteristics of their transmittal media that impact hardware requirements or indicate the need for logical or physical transformations before testing can begin (e.g., programs must be transferred from tape to disk).Items that are to be specifically excluded from testing may be identified.>
<In a narrative sections, focus on the key tested features. Address the points below.>
Identify all software features and combinations of software features tested. Provide reference to requirements for each feature.
Features not tested
Identify all features and significant combinations of features that were not tested and the reasons.
Item pass/fail criteria
Specify the criteria used to determine whether each test item has passed or failed testing.
Identify the set of tasks necessary to prepare for and perform testing. Identify all intertask dependencies and any special skills required.
Specify both the necessary and desired properties of the test environment. This specification should contain the physical characteristics of the facilities including the hardware, the communications and system software, the mode of usage (e.g., stand-alone), and any other software or supplies needed to support the test.
Also specify the level of security that must be provided for the test facilities, system software, and proprietary components such as software, data, and hardware.
Identify special test tools needed. Identify any other testing needs (e.g., publications or office space). Identify the source for all needs that are not currently available to the test group.
Identify the groups/person managed, designed, prepared, executed the test tasks.
These groups may include the developers, testers, operations staff, user representatives, technical support staff, data administration staff, and quality support staff.
Test Result Summary
Summarize the results of testing.
In an appendix, for each feature/combination of features tested, provide test cases used and the results of test cases, whether there are issues raised from the test result and the resolution of issues.>
<The Conclusion should constitute at least four paragraphs. More are acceptable, but the material suggested is to be addressed.
<Paragraph: Identify the result of the research effort as either “successful” or “requiring further work.” Indicate major tests and their results to support the conclusion.
<Paragraph: Compare the final state of the work with the original intent sought when the project was proposed. Include how the project could be extended into further versions.
<Paragraph: Discuss the ethical elements of the product. Include such items as privacy aspects, stewardship needs, security concerns, data access and integrity perspectives. Describe how your product attended to these ethical elements. Include points where ethical features remain to be addressed.
<Paragraph: Describe realization or potential for realization of benefits to the organization. Indicate how the product enables these benefits.
Quik Essay Services , written from scratch, delivered on time, at affordable rates!