PROGRAM 1- Implementation Specifications

Transcription

1 PROGRAM 1- Implementation Specifications Program Implementation Due Date: Feb 10, 2019 by 11:59pm (folder for next class meeting) You are to complete the following on your own unless otherwise stated. All programs must be written in C++ and be Linux compatible. Make sure you follow the Assignment Guidelines and Program Guidelines posted on my course webpage and use the templates provided. Implementation Deliverables Include the following in your program folder: (Staple in left top corner) Structure Chart (revised) make sure proper headings are included on SC One stapled packet: p1.cpp blank green rubric I will provide this in class by the folder due date Submit the following to my testing/grading directory: Submit your electronic files for grading- use the process outlined in Submit Directions p1t use this directory for testing your implementation p1f use this directory for grading your implementation Submit the following to D2L when implementation is complete: Submit Program 1 Work Log and Summary to D2L Assignments dropbox (one file) Create These Items 1. Structure Chart revision of the Structure Chart as you implement your program 2. p1.cpp contains the C++ solution to program 1 Provided Files Files for the program are provided in my directory: ~zimmer/csci230/192/p1/ Work Log and Summary Continue a single Word document from program 1 - design that contains the table of your work hours with your reflection summary below the table. This is due in the D2L Assignments dropbox by midnight on the day you turn in your program folder. Updated: 2/7/2019 1

2 Design, Implement and Test the following C++ Program A new role playing game is being design: Insurgence of the Predator Bugs. You are to write a program that processes files for the game. You are required to incorporate structures, unions(if needed), and enumerated data types into the implementation. The input file contains players for the game. The players are one of five types: EXPLORER, WARRIOR, HORNET, KILLERANT, or SPIDER. Each behaves either as a HUMAN or a BUG. HUMAN players belong to a coalition and BUG players belong to a swarm. Each player has attributes, but not all the same. The program should sort the players by type into separate files and maintain statistics about the file being processed. The program should count the number of players of each type and the number of melee weapons and range weapons. Create five output files and sort the records by the type of player (explorer, warrior, hornet, killerant, or spider). Input file of player data will be supplied to your program. The end-user will supply the name of the input file to be used. File formats are indicated later in this document. Once all the records have been processed the statistical information should be printed on the screen using the indicated column widths: 14 ch 8 ch 8 ch EXPLORER: number in file percent of file WARRIOR: number in file percent of file HORNET: number in file percent of file KILLERANT: number in file percent of file SPIDER: number in file percent of file MELEE: RANGE: TOTAL: number in file percent of file records using weapon number in file percent of file records using weapon total records processed Requirements You must use the following enum data types to store and process these values, you may not store char, string or int s for these fields in your player record in your program. PlayerType {EXPLORER, WARRIOR, HORNET, KILLERANT, SPIDER} WpnType {MELEE, RANGE} CoalitionType {VIGILANTE, GLOBAL, RESISTANCE} SwarmType {BEES, ANTS, SPIDERS} You must incorporate structures for player data and weapon data no scalar variables should be used for any of this data as it moves around your program. Updated: 2/7/2019 2

3 Example Test Runs: [20:22] $./p1.exe Please enter the input player file: players0.in playersx.in playersy.in players1.in ** NO RECORDS PROCESSED ** [20:24] $./p1.exe Please enter the input player file: playersx.in EXPLORER: % WARRIOR: % HORNET: 2 7.1% KILLERANT: % SPIDER: % MELEE: % RANGE: 0 0.0% TOTAL: 28 Updated: 2/7/2019 3

4 File Formats INPUT FILES Input file of players (user provides the name): HUMAN player record player_name#player_type#coalition#health#weapon_name#weapon_skill<linefeed> BUG player record player_name#player_type#swarm#health#armor_value<linefeed> * player_name will be one or more characters and may contain whitespace * player_type will be a single character ( E, W, H, K, S ) * coalition will be a single character ( V, G, R ) * swarm will be a single character ( B, A, S ) * health will be an int * armor_value will be an int * weapon_name will be one or more characters and may contain whitespace * weapon_skill will be an int * <line feed> is a new line character ( \n ) ** all character input could be upper or lowercase weapons.in weapon_name#weapon_type#weapon_damage<linefeed> * weapon_name will be one or more characters and may contain whitespace * weapon_type will be a single character ( M, R ) * weapon_damage will be an int * <line feed> is a new line character ( \n ) OUTPUT FILES explorers.out, warriors.out player_name#player_type#coalition#health#weapon_name#weapon_skill<linefeed> hornets.out, killerants.out, spiders.out player_name#player_type#swarm#health#armor_value<linefeed> * output the same values as used for input files Updated: 2/7/2019 4

5 Programmer: Score: /100 Program 1 - Implementation Rubric Outstanding 4-5 points Developing 2-3 points Needs Improvement 0-1 point Structure Chart Proper structure, organized, and complete Small structure issue or a few missing details Structure incorrect or incomplete or missing Documentation The documentation is well written The documentation consists of and clearly explains what the code some simple header is accomplishing and how. documentation that is somewhat Includes clearly stated pre/post useful in understanding the code. conditions. The documentation is some simple header comments separating routines. Readability The code is exceptionally well The code is mostly easy to read. organized and very easy to follow. The code is readable only by someone who knows what it is supposed to be doing. Implementation Requirements All implementation items done per specifications. Some items do not meet required specifications Many items are not implemented per specifications Memory management No extra fields or misc variables were created. Some misuse of variables and fields. Poor use of memory. Reusability The code is created with reusability in mind and code reuses when needed. Most of the code uses reusable code when possible. Little attention was paid to reusability. Efficiency The code is extremely efficient The code is mostly efficient The code is brute force and without sacrificing readability and without sacrificing readability and unnecessarily long. understanding. understanding. Outstanding points All functions work and meet all of the specifications. Developing points Most functions work and produce correct solutions. Needs Improvement 0-25 points Some functions work, many do not produce correct solutions. Specifications 2/7/2019 CSCI230 Spring 2019 (192)