Intermediate software development, Software Engineering

Provide an abstract superclass called EnergyRecord and subclasses called Contract and Transaction with default constructors (no-arg) and full-arg, overloaded constructors. Collect abstract commonality in the superclass to be inherited into the subclasses.

Provide instance fields, instance accessor and mutator methods for all of the data fields in each record data files. If no value is provided in the FERC data, then set that characteristic to some default value.

Provide a toString() method to format all of the record data in each class.

Provide an interface called TransactionRelatable with four methods:

  • boolean isTransactionChargeSmaller(Object other );
  • double findTransactionChargeDifference(Object other);
  • boolean isTransactionQuantityGreater(Object other);
  • double findTransactionQuantityDifference(Object other);

Implement this interface in the EnergyRecord class.

Provide a driver class that includes the following features:

  • creates an instance of each energy record class for each row in the two files
  • collects all contract objects into an array of EnergyRecord called contracts
  • collects all transaction objects into an array of TransactionRelatable called transactions
  • displays all contract data using the toString() method in a loop
  • displays all contract and transaction data in a tabular format using accessor methods
  • displays the comparisons of the transaction_chargeĀ  of any two transactions
  • displays the comparisons of the transaction_quantity of any two transactions
  • displays the minimum price of all transactions
  • displays the maximum units of all transactions.

Provide a test script called test_mp1.bat in the test folder to execute the project and send its output to a file called test_mp1_out.txt.

Comment your code and provide a detailed README (pdf only) file that includes:

  • project description
  • installation, compile and run-time requirements
  • development and testing insights with expected results
  • screen captures demonstrating all application capabilities
  • generate project javadocs documentation
  • minimize your main() method code by using intuitive functions

Submit a file called mp1.zip (zip format only) of all project code and documentation to the Digital DropBox link on Blackboard by 09/18/11, 23:59/CST. Note that a completed submission requires the use of both the Add File button and the Send File button. A late mini-project will lose more points the later that it is submitted.

Posted Date: 3/19/2013 3:16:15 AM | Location : United States







Related Discussions:- Intermediate software development, Assignment Help, Ask Question on Intermediate software development, Get Answer, Expert's Help, Intermediate software development Discussions

Write discussion on Intermediate software development
Your posts are moderated
Related Questions
Question 1 Write short notes on (i) Lexical Analysis (ii) Syntax Analysis (iii) Semantic Analysis 2 Explain various data structures used in Macro Processor Design 3 Descr

How do you develop a test plan and schedule? Describe bottom-up and top-down approaches. A test plan is contract among the testers and the project team explaining the role of t

what effect does memory have on dma? what about on board cache? how much are the system buses available?

Question: a) Briefly describe the principles of the DSDM methodology. b) What are the advantages of using the DSDM methodology? c) The MOSCOW technique is used to priori

differentiate between structured analysis and structured design

What are the advantages of evolutionary prototyping? i. Fast delivery of the working system. ii. User is included while developing the system. iii. More useful system can

#question2. Explain any ten CASE tools...

I am currently working on a project and am far from passing, I need help ASAP! The project task is to create a Decision support system for An Airline. It must predict and make de

Define coupling. Coupling is the measure of the degree of interdependence among modules.

Documentation explaining plans for, or results of, the testing of a system or component, Types contain test case specification, test incident report, test log, test procedure, test