Free Essay

Requirement Specification

In:

Submitted By rass667
Words 1891
Pages 8
Moji Weather
Requirements Specification

Authors and Contributions Name | Contribution in % | Ideas, Concepts | Parts of the Specification | | | | | | | | | | | | | | | | | | | | |

Prof. Dr. Samuel A. Fricker
Mini Project Requirements Engineering
Moji Weather
Spring 2016

About the Template v1.1E- Spring 2016
The template has been developed for the requirements engineering course offered by Samuel Fricker. The use of the document is continuously reviewed and adapted if necessary. Please direct feedback and recommendations to samuel.a.fricker@gmail.com.
The template is useful for projects that aim at conceiving and developing consumer-oriented software products that may be realized by a team of young software engineers. This template is a tool that may be used to define a software that is as simple as possible and generates as much value as possible.
Each chapter features instructions on what to document. The author of the requirements specification shall not hesitate to adapt the chapter structure. Also, the texts in the template shall be removed and replaced by the actual requirements.
Advise for structuring the contents of a chapter: * Start with a short introduction that describes the role of the chapter and in what relation the chapter is to previous chapters. * Short summary of the chapter contents. * Overview picture or diagram. * Details in tables, texts, and diagrams on a detail level.
Good luck and lots of fun in the discovery of what can be done with software!
/Samuel Fricker

Revisions Version | Date | Comment | Author | Version 0.1 | 20.03.2016 | Template | Samuel Fricker | | | | |

Contents 1 Introduction 5 1.1 The Team 5 1.2 Requirements Engineering Process 5 2 Problem 5 2.1 Background 5 2.2 Goals of a Successful Solution (Product Goals) 6 2.3 Evaluation of Existing Alternatives 6 3 Concept: Moji Weather 9 3.1 Key Idea 9 3.2 Viewpoints 10 3.3 Features 10 3.4 Constraints 11 4 Requirements 12 5 Appendices 12 5.1 Glossary 12 5.2 Future Requirements 13 5.3 Everything Else 13

Introduction
The Team
Short description of the team members, of their backgrounds, and why the team has chosen the here documented future software product.
Min Yuhao
Qi Pengyang
Ruan Yizhang
Zhu Zhanheng
Dong Panhang

Requirements Engineering Process
Summarize how you have elicited, analysed, documented, and validated the requirements. Justify your approach. Explain to what extent the requirements reflect an innovative product that meets true needs.

Problem
Background
The problem that motivates users and customers to use the software system that is specified in the remaining sections.
Formalize the problem description with the following elements of the RUP vision template: * The problem of * Affects * The impact of which is…
Describe the evidence you have, which shows that the problem truly exists and is supported by the software system’s stakeholders.
-------------------------------------------------
Recommendation for Visualization:
- Use Context (with photographs)

Weather is always an important topic in everyone’s life. Not only the weather disaster, such as hurricane and hail, can be life-threatening, but our daily life, activity arrangement, clothing and so on also need to rely on weather report. Although, weather report service can be get from television, radio, newspaper and other traditional media, but they are not portable and instantly.

The problem of: do not know whether to bring an umbrella or not; do not know what to wear; do not know when to hold an activity;
Affects: the public;
The impact of which is: get wet in the rain; suffer from heatstroke; suffer from cold; hold an activity in the rain.

Goals of a Successful Solution (Product Goals)
Criteria for deciding if a solution of the problem is successful. This sub-chapter corresponds to the entry “a successful solution would be…” of the RUP vision template. * Name of the goal (so that you can refer to it), * Description of the goal (what the goal is, why the goal is important and who, besides the customer, may also be affected by it), * Measurement of goal achievement (quantitative criteria for determining when the goal is considered to be achieved)
A successful solution would be: * Good coverage: cover most of the cities in the country. * Air quality: provide air quality information including PM2.5, PM10, SO2, etc. * Weather forecast for next 15 days: provide accurate weather information for the upcoming 15 days. * Suggestions of clothing: tell you what to wear that will make you feel comfortable. * Voice broadcast: read out the information when you are busy doing other things. * Extreme weather alert: push notification when an extreme weather is coming, so you can prepare for it.

Evaluation of Existing Alternatives
What the users and customers have used so far and what other alternatives they could use to solve the problem. Explain why these alternatives are not good enough for achieving the product goals. * Name of the alternative (so that you can refer to it) and description (what the alternative is) * Limitations (why the alternative is not good enough for solving the users’ problem) * Implications for your software (describe what you can re-use and what should be done differently)
-------------------------------------------------
Recommendation for Visualization:
- Appearance of the solution (screen shots or photo documentation)
Traditional medium:
Many traditional medium, such as television, radio, newspaper, and so on, offer weather forecast service. But they have a lot of limitations. For example, they are lack of portability and instantaneity.

Other weather applications:
There are many weather applications in the market. Each application has its advantages and drawbacks. Below, we list three of the most popular weather apps in Google Play Store.

The Weather Channel
This is a weather application provide by The Weather Channel. The Weather Channel is an American basic cable and satellite television channel, owned by a consortium made up of The Blackstone Group, Bain Capital, and NBC Universal.

Pros: Weather Channel data. Handy subtle widgets. Slick new interface. Pollen and airport dalay data. New social weather feature.
Limitations: do not fully support Simplified-Chinese; lack of information;
Implications:

Weather Underground
The Internet's first ever weather site, Weather Underground has built a reputation for providing the most reliable and in-depth weather data for locations across the world. With our unique network of 180,000+ neighbourhood weather stations our app provides the most localized weather information available.

Limitations: do not fully support Simplified-Chinese; lack of information;
Implications:

Yahoo Weather

Pros: Slick design. Flickr images. Numerous widgets. Customizable stream.
Cons: Occasionally sluggish. Few radar map options.
Implications:

Concept: Moji Weather
Key Idea
Describe the key idea of your software system, who will be using the software system, and how the software system allows achieving the product goals.
Summarize the concept by formalizing it with the following elements of the RUP vision template:
-------------------------------------------------
Recommendations for diagrams (and notations or visualizations):
- direct system context (data flow diagram or class diagram)
- use process (BPMN, storyboard, or photo story)
Describe the evidence you have, which shows that the concept works and that the product goals are fulfilled.

For the public;
Who work / go outside;
The weather information provider;
That give information about weather;
Unlike traditional medium is not portable or instant; other weather applications just offer some data;
Our solution gives suggestions (bring / not bring umbrella, what to wear), extreme weather alerts.

Viewpoints
Consider the following viewpoints: * The various user groups * The customer * The provision of the back-end cloud, the app store, and other distribution channels * Third-party systems that your system interoperates with * Other (people, groups, or organizations
-------------------------------------------------
Recommendations for diagrams (and notations or visualizations):
- overview of viewpoints (onion model)
Define for each viewpoint: * Name of the viewpoint (so that you can refer to it) * Characterization (criteria to decide whether a given person matches the role characterized by the viewpoint) * Background (the knowledge of the stakeholders that represent the viewpoint) * Goals (the desired impact of the software on the stakeholders that represent the viewpoint; the goals should be motivating the use of the software) * Representatives (Name, address, etc.) to be involved in requirements engineering

Features
The most important features of the software, which are needed for the achievement of the product goals. A good way to conceive features is to consider the various types of data that are created and managed with the application. Sort the features according to priority for development (at the top the feature that is to be implemented first).
Define for each feature: * Name (so that you can refer to it) * Priority (affects the order of development) * Cost (effort and expenses; affects the order of development) * Short description (what the feature is) * Goals (the impact of the feature on the viewpoints, respectively the fulfilment of the product goal) * Implementation (key idea for implementing the feature)
Check Present Weather Condition:

Check Weather Forecast:

Get Suggestions for Daily Life:

Get Extreme Weather Alert:

Constraints
Decisions that have been imposed by stakeholders and, as a consequence, have to be respected by project management, software system architecture, implementation or testing.
Define for each constraint: * Short description (what the feature is and why it is important for the stakeholders)

Requirements
Check Present Weather Condition

Structure this potentially long chapter so that themes that belong together are put into one single sub-chapter. If possible, create one sub-chapter for each feature. Sort the sub-chapters according to priority in the development (first the sub-chapter that is to be implemented first).
The writing of the chapter depends on the selection of appropriate notations. Transfer actively the course contents (do not re-invent the wheel).

-------------------------------------------------
Recommendations for the structuring of chapter 4:
- Per feature one sub-chapter. Each feature should be scoped so that it makes sense for the user but is still as small as possible. Extensions of a minimal feature should again be presented as a feature and also be listed in chapter 3.3.
- for the totality of quality requirements of the application, consider the definition of one sub-chapter.
-------------------------------------------------
Each sub chapter has the following structure:
- Identifier and name (copy/paste from chapter 3.3).
- Short description (copy/paste from chapter 3.3).
- Short description of how you have elicited, analysed, and validated the feature.
- Short description of the sub-chapter (explanation for the reader of what he/she will be reading. Refer to the diagrams with the help of legends.
- Overview (UML use case diagram).
- Catalogue of use scenarios (use cases as tables with use case attributes and structured text; the flow may also be specified as a UML activity diagram). - The system functionality that is needed to support the use case: requirements backlog (according to selected language template).
- Domain model (UML class diagram). - For important classes: behaviour (UML state machine diagram).
- Graphical user interfaces (wireframes).
- Feature-specific quality requirements.
-------------------------------------------------
Note: adapt the structure of the sub-chapters to minimize the need for text and graphics. Avoid unnecessary information and redundancies as far as possible.
-------------------------------------------------
Note: each content (feature, use case, requirement, class, etc.) shall have a unique identifier that allow unambiguous referencing of that content.
-------------------------------------------------
Note: depending on the software system you may need to change the structure of this chapter. Discuss your proposal with the lecturer.

Appendices
Glossary
Define here the terms and abbreviations that are used in the requirements specification.

Future Requirements
Document the list of the desired improvements, respectively changes of the software that should be realized after your project.

Everything Else
Refer to documents, models, photos, videos, etc., which should be used for understanding the requirements or as evidence that confirms the correctness of the requirements.

Similar Documents

Premium Essay

Software Requirement Specification

...Software Requirements Specification Template CptS 322—Software Engineering 9 February 2005 The following annotated template shall be used to complete the Software Requirements Specification (SRS) assignment of WSU-TC CptS 322. The instructor must approve any modifications to the overall structure of this document. Template Usage: Text contained within angle brackets (‘’) shall be replaced by your project-specific information and/or details. For example, will be replaced with either ‘Smart Home’ or ‘Sensor Network’. Italicized text is included to briefly annotate the purpose of each section within this template. This text should not appear in the final version of your submitted SRS. This cover page is not a part of the final template and should be removed before your SRS is submitted. Acknowledgements: Sections of this document are based upon the IEEE Guide to Software Requirements Specification (ANSI/IEEE Std. 830-1984). The SRS templates of Dr. Orest Pilskalns (WSU, Vancover) and Jack Hagemeister (WSU, Pullman) have also be used as guides in developing this template for the WSU-TC Spring 2005 CptS 322 course. Software Requirements Specification Lead Software Engineer Prepared for WSU-TC CptS 322—Software Engineering Principles I Instructor: A. David McKinnon, Ph.D. Spring 2005 Revision History Date Description Author Comments Document Approval The following...

Words: 1662 - Pages: 7

Premium Essay

Software Requirements Specification

... | | | | | |Software Engineering | |MedPulse | |Software Requirements Specification | | | |...

Words: 3076 - Pages: 13

Premium Essay

Software Requirement Specification

...< Project scenario name > Software Requirements Specification Version < X.0> < team Name > < Scenario Name > Software Requirements Specification Version < X.0> Team Guide:( Faculty Guide’s Name ) Members:(Team members name) College Name: Department: State: / Page 1 < Project scenario name > Software Requirements Specification Version Revision History Date Version 1.0 2.0 Description Synopsis Synopsis Author / Page 2 < Project scenario name > Software Requirements Specification Version X.0 Table of Contents Description 1.0 Introduction 1.1 1.2 1.3 1.4 1.5 1.6 Purpose Scope Definition, Acronyms, and Abbreviations References Technologies to be used Overview Page No. 2.0 Overall Description 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 Product Perspective Software Interface Hardware Interface Product Function User Characteristics Constraints Architecture Design Use Case Model Description / Page 3 < Project scenario name > Software Requirements Specification Version X.0 2.9 Class Diagram ........................................................................ Sequence Diagram s ............................................................... 2.10 Database Design .................................................................... 2.11.1 2.11.2 ER Diagram ............................................................... Schema ...................................................................... 2.12...

Words: 739 - Pages: 3

Premium Essay

Software Requirement Analysis and Specification

...Abstract:-Software requirement analysis is a method to find out the requirements form the user to develop software. Software requirement analysis and specification also include the types of user requirements and the methods by which developer team can elicit the user requirement and develop suitable software for the user. Introduction:- ➢ Requirement analysis: - Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management. Requirements analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project development process from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs rather than attempting to mold user expectations to fit the requirements. Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people. ➢ Software requirement analysis: - The success of any new software...

Words: 2585 - Pages: 11

Premium Essay

Software Requirements Specification Document

...Software Requirements Specification for Mountain Bank Cell Phone App Version 5.0 approved CS455/Techs2ATee May 11, 2015 Table of Contents 1. Introduction 1 1.1 Purpose 1 1.2 Document Conventions 1 1.3 Intended Audience and Reading Suggestions 2 1.4 Project Scope 2 1.5 References 3 2. Overall Description 6 2.1 Product Perspective 6 2.2 Product Features 6 2.3 User Classes and Characteristics 7 2.4 Operating Environment 7 2.5 Design and Implementation Constraints 7 2.6 User Documentation 8 2.7 Assumptions and Dependencies 8 3. System Features 9 3.1 Establish Secure Session 9 3.1.1 Description and Priority 9 3.1.2 Stimulus/Response Sequences 9 3.1.3 Functional Requirements 9 3.1.4 Secure Session Test Script 10 3.2 Login 12 3.2.1 Description and Priority 12 3.2.2 Stimulus/Response Sequences 12 3.2.3 Functional Requirements 12 3.3 View Balances 13 3.3.1 Description and Priority 13 3.3.2 Stimulus/Response Sequences 13 3.3.3 Functional Requirements 13 3.4 View Transaction History 14 3.4.1 Description and Priority 14 3.4.2 Stimulus/Response Sequences 14 3.4.3 Functional Requirements 14 3.5 Transfer Funds 15 3.5.1 Description and Priority 15 3.5.2 Stimulus/Response Sequences 15 3.5.3 Functional Requirements 15 3.5.4 Funds Transfer between Accounts Test Script 16 3.6 Deposit 20 3.6.1 Description and Priority 20 3.6.2 Stimulus/Response Sequence 20 3.6.3 Functional Requirements 20 3.6.4 Successful Deposit Test Script 21 4. External...

Words: 13282 - Pages: 54

Premium Essay

Software Requirement Specification of Library Mgmt System

...SOFTWARE REQUIREMENTS SPECIFICATION For Library Management System Prepared by:- Soumili Sen Nayan Patil Neha Singh Anita Singh Academic Year: 2013-2014 1. Introduction 1.1 Purpose The main objective of this document is to illustrate the requirements of the project Library Management system. The document gives the detailed description of the both functional and non-functional requirements proposed by the client. The purpose of this project is to provide a friendly environment to maintain the details of books and library members. The main purpose of this project is to maintain easy circulation system using computers and to provide different reports. This project describes the hardware and software interface requirements using ER diagrams and UML diagrams. 1.2 Document Conventions * Entire document should be justified. * Convention for Main title * Font face: Times New Roman * Font style: Bold * Font Size: 14 * Convention for Sub title * Font face: Times New Roman * Font style: Bold * Font Size: 12 * Convention for body * Font face: Times New Roman * Font Size: 12 1.3 Scope of Development Project Library Management System is basically updating the manual library system into an internet-based application so that the users can know the details of their accounts, availability of books and maximum limit for borrowing. The project is specifically designed for the use of librarians and library users...

Words: 2807 - Pages: 12

Free Essay

Software Requirements Specification

...SOFTWARE REQUIREMENTS SPECIFICATION RFID Parking Garage Anthony Nichols Matthew Nichols 1.0 Introduction Finding parking spaces for automobiles and motorcycles can a problematic venture due to limited space and time, while the selling of parking spaces is potential lucrative endeavor. Currently, most large parking garages, including airport parking, use a ticketing system in which users get a time-stamped ticket when entering the structure and pay a time relative fee when exiting. The transmission of these disposable tickets is a time inefficient process susceptible to error. These tickets can easily be lost, and with the lost tickets, the entire process disoriented. The manual payment process can also be time consuming when traffic is at a high rate. An RFID parking system would improve this by allowing the user to interact with the parking area with an RFID card at the entrance and exit of the parking area. An RFID parking system would also allow the user to keep an account on which the system would keep track of financial transactions. This would reduce the amount of time the user must interact with the system and increase the security of the user. A new system to allow ease of use and increased security of parking areas is needed 1. Goals and objectives • To provide individuals who require a parking area with a system that is efficient and easy to use. • To provide individuals with a system that accounts for the length of each visit and...

Words: 2239 - Pages: 9

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Cis 331 Week 4 Case Study 1: Software Requirement Specification

...CIS 331 Week 4 Case Study 1: Software Requirement Specification Click Link Below To Buy: http://hwcampus.com/shop/cis-331-week-4-case-study-1-software-requirement-specification/ Or Visit www.hwcampus.com Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Write a three to five (3-5) page paper in which you: 1. Create a Software Requirement Specification (SRS) that includes the following: 1. A detailed description of both user and system requirements. At least four (4) user requirements and four (4) system requirements should be provided. 2. A detailed description of both functional and nonfunctional requirements. At least four (4) functional requirements and four (4) nonfunctional requirements should be provided. 3. A detailed requirement specification written in structured natural language. 2. Structure and present the requirements in a logical and consistent manner. 3. Develop a use case diagram to summarize the functional requirements of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length. Your assignment must follow these formatting requirements: • Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions...

Words: 376 - Pages: 2

Premium Essay

Orion Project

...such an effort. He had no trouble getting functional support for the R&D effort necessary to put together a technical proposal. All of the functional managers continually remarked to Gary "This must be a biggy. The director of engineering has thrown all of his support behind you." On December 2, the RFP was received. Gary identified one trouble area. The technical specifications stated that all components must be able to operate normally and successfully through a temperature range of -65 degrees F to 145 degrees F. Current testing indicated the Scientific Engineering Corporation design would not function above 130 degrees F. An intensive R&D effort was conducted over the next three weeks. Everywhere Gary looked, it appeared that the entire organization was working on his technical proposal. Gary and Henry Larsen met a week before the final proposal was due to develop a company position concerning the inability of the preliminary design material to be operated above 130 F. Gary was concerned. Every approach he tried indicated that the original design wouldn't work. He didn't think the specification requirements could be met without a change in materials. Gary wanted to tell the customer the truth, let the chips fall where they may and start over, and he told Larsen this. But Larsen had a different approach. Henry Larsen. Watch Video | Read Transcript The proposal was submitted after two solid months of sixteen-hour days. On February 10, Space Technology Industries...

Words: 279 - Pages: 2

Premium Essay

Unit 3: Lab 1: Building a New Structure - Nfpa Codes

...variety of existing and future services, using industry accepted design and installation methods. To define standards that will enable the design and implementation of structured cabling systems for commercial buildings and between buildings. The telecommunications industry standards, codes and practices are defined in various state and agencies on web sites defined in a catalog that can purchase and downloaded and read for immediate enforcement of these guidelines used for each industry. These policies are intended to answer faxes of infrastructure practices and not to be a substitute for knowledge of industry accepted practices, standards and codes. Policies are not intended to be used in lieu of a construction specification document, are used to abide to the specifications. Communications technologies can be complex and designed and installed by experienced professionals. Telecommunications are considered a fourth utility, to be designed, funded and installed with the same importance as Electrical, Plumbing and HVAC. The designer has the responsibility of providing a design using accepted engineering and architectural practices and recommends a Registered Communications Distribution Designer (RCDD) to be used as a consultant for the design of the telecommunications. In many cases the need will arise to consult with other engineers from other trades or...

Words: 1394 - Pages: 6