The Republic Of Angol The Popular Movement For The...

Introduction The Republic of Angola is a country located in the south-western part of Africa. Angola is north of Namibia, south of Democratic Republic of the Congo, and west of Zambia. Before it gained independence in 1975, Angola was a colony under Portugal’s rule. After Angola’s independence, the country fell into a civil war that lasted for 27 years. There were two major forces in the civil war: the Popular Movement for the Liberation of Angola (MPLA) and the Total Independence of Angola (UNITA). Even though Angola is still recovering from the war, its real GDP has been growing ever since the end of the civil war. Economy Key Terms: -GDP stands for gross domestic product, and it is the value of all goods and services produced inside the country. It is calculated by adding government spending, household consumption, investments and savings, exports, and subtracting imports. -PPP stands for purchasing power parity, and it is the adjustments made to the GDP figures so that the same amount of money would be able to buy the same basket of goods anywhere in the world. -GDP per capita is dividing the GDP by the population and getting an estimate of how much money the average person makes annually in the country. -Expansion is increasing GDP in 2 consecutive quarters. -Recession is decreasing GDP in 2 consecutive quarters. Angola’s GDP composition: Most of Angola’s GDP is household consumption. Second biggest is government spending due to money spent on reconstruction after

Software Requirements Specification Template Free Essays

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. We will write a custom essay sample on Software Requirements Specification Template or any similar topic only for you Order Now 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. 30-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 Approva l The following Software Requirements Specification has been accepted and approved by the following: |Signature |Printed Name |Title |Date | | | |Lead Software Eng. | | | |A. David McKinnon |Instructor, CptS 322 | | | | | | | Table of Contents Revision Historyii Document Approvalii 1. Introduction1 1. 1 Purpose1 1. 2 Scope1 1. 3 Definitions, Acronyms, and Abbreviations1 1. 4 References1 1. 5 Overview1 2. General Description2 2. 1 Product Perspective2 2. 2 Product Functions2 2. 3 User Characteristics2 2. 4 General Constraints2 2. 5 Assumptions and Dependencies2 3. Specific Requirements2 3. 1 External Interface Requirements3 3. 1. 1 User Interfaces3 3. 1. 2 Hardware Interfaces3 3. 1. 3 Software Interfaces3 3. 1. 4 Communications Interfaces3 3. 2 Functional Requirements3 3. 2. 1 3 3. 2. 2 3 3. 3 Use Cases3 3. 3. 1 Use Case #13 3. 3. 2 Use Case #23 3. Classes / Objects3 3. 4. 1 3 3. 4. 2 3 3. 5 Non-Functional Requirements4 3. 5. 1 Performance4 3. 5. 2 Reliability4 3. 5. 3 Availability4 3. 5. 4 Security4 3. 5. 5 Maintainability4 3. 5. 6 Portability4 3. 6 Inverse Requirements4 3. 7 Design Constraints4 3. 8 Logical Database Requirements4 3. 9 Other Requirements4 4. Analysis Models4 4. 1 Sequence Diagrams5 4. 3 Data Flow Diagrams (DFD)5 4. 2 State-Transition Diagrams (STD)5 5. Change Management Process5 A. Appendices5 A. 1 Appendix 15 A. 2 Appendix 25 1. Introduction The introduction to the Software Requirement Specification (SRS) document should provide an overview of the complete SRS document. While writing this document please remember that this document should contain all of the information needed by a software engineer to adequately design and implement the software product described by the requirements listed in this document. (Note: the following subsection annotates are largely taken from the IEEE Guide to SRS). 1. 1 Purpose What is the purpose of this SRS and the (intended) audience for which it is written. 1. 2 Scope This subsection should: (1) Identify the software product(s) to be produced by name; for example, Host DBMS, Report Generator, etc (2)Explain what the software product(s) will, and, if necessary, will not do (3)Describe the application of the software being specified. As a portion of this, it should: (a) Describe all relevant benefits, objectives, and goals as precisely as possible. For example, to say that one goal is to provide effective reporting capabilities is not as good as saying parameter-driven, user-definable reports with a 2 h turnaround and on-line entry of user parameters. (b) Be consistent with similar statements in higher-level specifications (for example, the System Requirement Specification) , if they exist. What is the scope of this software product. 1. 3 Definitions, Acronyms, and Abbreviations This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the SRS. This information may be provided by reference to one or more appendixes in the SRS or by reference to other documents. 1. 4 References This subsection should: (1)Provide a complete list of all documents referenced elsewhere in the SRS, or in a separate, specified document. 2)Identify each document by title, report number – if applicable – date, and publishing organization. (3)Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document. 1. 5 Overview This subsection should: (1) Describe what the rest of the SRS contains (2) Explain how the SRS is organized. 2. General Description This section of the SRS should describe the general factors that affect ‘the product and its requirements. It should be made clear that this section does not state specific requirements; it only makes those requirements easier to understand. 2. 1 Product Perspective This subsection of the SRS puts the product into perspective with other related products or projects. (See the IEEE Guide to SRS for more details). 2. 2 Product Functions This subsection of the SRS should provide a summary of the functions that the software will perform. 2. 3 User Characteristics This subsection of the SRS should describe those general characteristics of the eventual users of the product that will affect the specific requirements. (See the IEEE Guide to SRS for more details). 2. 4 General Constraints This subsection of the SRS should provide a general description of any other items that will limit the developer’s options for designing the system. See the IEEE Guide to SRS for a partial list of possible general constraints). 2. 5 Assumptions and Dependencies This subsection of the SRS should list each of the factors that affect the requirements stated in the SRS. These factors are not design constraints on the software but are, rather, any changes to them that can affect the requirements in the SRS. For example, an assumption might be that a specific operating system will be available on the hardware designated for the software product. If, in fact, the operating system is not available, the SRS would then have to change accordingly. 3. Specific Requirements This will be the largest and most important section of the SRS. The customer requirements will be embodied within Section 2, but this section will give the D-requirements that are used to guide the project’s software design, implementation, and testing. Each requirement in this section should be: †¢ Correct †¢ Traceable (both forward and backward to prior/future artifacts) †¢ Unambiguous †¢ Verifiable (i. e. , testable) †¢ Prioritized (with respect to importance and/or stability) †¢ Complete †¢ Consistent †¢ Uniquely identifiable (usually via numbering like 3. 4. 5. 6) Attention should be paid to the carefuly organize the requirements presented in this section so that they may easily accessed and understood. Furthermore, this SRS is not the software design document, therefore one should avoid the tendency to over-constrain (and therefore design) the software project within this SRS. 3. External Interface Requirements 3. 1. 1 User Interfaces 3. 1. 2 Hardware Interfaces 3. 1. 3 Software Interfaces 3. 1. 4 Communications Interfaces 3. 2 Functional Requirements This section describes specific features of the software project. If desired, some requirements may be specified in the use-case format and listed in the Use Cases Section. 3. 2. 1 3. 2. 1. 1 Introduction 3. 2. 1. 2 Inputs 3. 2. 1. 3 Processing 3. 2. 1. 4 Outputs 3. 2. 1. 5 Error Handling 3. 2. 2 †¦ 3. 3 Use Cases 3. 3. 1 Use Case #1 3. 3. 2 Use Case #2 †¦ 3. 4 Classes / Objects 3. 4. 1 3. 4. 1. 1 Attributes 3. 4. 1. 2 Functions 3. 4. 2 †¦ 3. 5 Non-Functional Requirements Non-functional requirements may exist for the following attributes. Often these requirements must be achieved at a system-wide level rather than at a unit level. State the requirements in the following sections in measurable terms (e. g. , 95% of transaction shall be processed in less than a second, system downtime may not exceed 1 minute per day, ;gt; 30 day MTBF value, etc). 3. 5. 1 Performance 3. 5. 2 Reliability 3. 5. 3 Availability 3. 5. 4 Security 3. 5. 5 Maintainability 3. 5. 6 Portability 3. 6 Inverse Requirements State any *useful* inverse requirements. 3. 7 Design Constraints Specify design constrains imposed by other standards, company policies, hardware limitation, etc. hat will impact this software project. 3. 8 Logical Database Requirements Will a database be used? If so, what logical requirements exist for data formats, storage capabilities, data retention, data integrity, etc. 3. 9 Other Requirements Catchall section for any additional requirements. 4. Analysis Models List all analysis models used in developing specific requirements previously given in this SRS. Each model should include an introduction and a narrative description. Furthermore, each model should be traceable the SRS’s requirements. 4. 1 Sequence Diagrams 4. 3 Data Flow Diagrams (DFD) 4. 2 State-Transition Diagrams (STD) 5. Change Management Process Identify and describe the process that will be used to update the SRS, as needed, when project scope or requirements change. Who can submit changes and by what means, and how will these changes be approved. A. Appendices Appendices may be used to provide additional (and hopefully helpful) information. If present, the SRS should explicitly state whether the information contained within an appendix is to be considered as a part of the SRS’s overall set of requirements. Example Appendices could include (initial) conceptual documents for the software project, marketing materials, minutes of meetings with the customer(s), etc. A. 1 Appendix 1 A. 2 Appendix 2 How to cite Software Requirements Specification Template, Papers

Comparison of tones used by Phillis Wheatley and F Essay Example For Students

Comparison of tones used by Phillis Wheatley and F Essay rederick DouglassTwo of the most well known black writers that were for the abolishnist movement in America were Frederik Douglass and Phillis Wheatley. At a time when a literate Negro would have only existed in a nightmare and when even the majority of the white women in the country were illiterate, these two authors of distinguished valor managed to write literature and recite speeches that inspired some of the most impenetrable minds to change their ways of thinking. Wheatley would move her readers with her subtle, yet powerful literature while Douglass would do the same with his powerful use of words. Phillis Wheatley was one of the more passive abolishionist writers. Because she was a slave and she was aware of her position in society as opposed to the whites, she knew that enfuriating her audience was the wisest thing to do.When criticizing slavery she chose her words very wisely. In her poem On Being Brought from Africa to America, for example, she does not blatantly protest about slavery and call her readers savages like Douglass would do. Instead she and realized has realized her position in serialized her position in society as a slave and In her literature she criticizes slavery through rli Although, Phillis Wheatley was an abolishnist writer, she passive than a lot of her literature didnt always reflect. At first glance it would For a man going against a legion of non-followers, Frederik Douglass held nothing back. Wheatley, Unlike unFor an abolishnist writer, one mustand Although they both took very diifrent approaches very, but also managed to get their works published. Wheatley would move the crowed inspire authors wrote poetry ab it was a forbidden for a Negros to learn how to readblack to learn how to read andbeing literate being illeterate was law for blacks, and women ere being illetarate for Wheatley and Douglass wroteAt a time where it was forbidden for a Negro to learn how to read and even majority of the white women couldnt read, Phillis and Wheatley were writing verses that were so powerfulwthese two a uthors, managed to recite speeches and write sonnets to get to n blacks werent to learn how to read or write or evenallowed to be literate and even white werent allowed to be even women werent allowed forced to be illeterate and were not Although, there apporaches were different theAlthough they would bothWheatley would getting her point across with her subttle but powerful poems while Douglass would Although, they were both very different in their approaches, they managed to overcome what at the manwere both successful inPhillis Wheatley was the With their wit and charisma, these two are two main