Program 2, TCSS 380 Autumn 2019
OBJECTIVE
The objective of this assignment is to apply your newly learned Erlang knowledge to build a program from scratch.
ASSIGNMENT DESCRIPTION
For this assignment you will rewrite the programming assignment you have done in C. All highlevel program logic remains the same. Since, however, now you are modelling this logic in Erlang, the following requirements must be met:
Each directory entryfile in the program is to be modeled by a tuple that consists of a filename and its size in bytes that will be entered by the user, and the number for the beginning block and the number of blocks used by the file that will be generated by the program
The directory table should be modeled by a list
Each block in the program is to be modeled by a tuple that consists of a block number, how much of this
block is used and the amount of internal fragmentation
The block table should be modeled by a list
IO: Since we havent discussed interactive input, examine the small sample functions below for interactive input handling.
integer input handling:
input
Sio:getlineEnter: , Int,string:tointegerS, io:fwriteecho i n, Int, case Int of
1234
end.
string input handling:
input
Sio:getlineprompt: , Strip,lists:splitlengthS1, S, io:fwriteecho s n, Strip, case string:equalStrip, quit of
truedone; input
end.
Your program is to include the following functions follow the naming conventions if you want your program to be graded:
mymain this function is similar in its logic to how main functions in C and Java, i.e. starts and drives the program; the user will call this function from the shell in order to start the program
printMenu prints the menu choices to the shell
blocksAsString ListOfBlockTuples given a list of tuples representing the blocks returns that list as a string
directoryAsStringListOfFileTuples given a list of tuples representing the files returns that list as a string
other functions you deem appropriate to achieve proper modularization
In addition, your program must fulfill the following requirements:
Only lists and tuples are to be used, no other data structures allowed
Your driver file should be called pr2.erl
Helper functions should NOT be listed in an export statement
Include commentsthe header with your name, program name, date; function headers that describe the
purpose of each function; code comments that describe the highlevel logic
Your program is to be contained within one file called pr2.erl ; If you decide to use a multiple file structure,
you can call your other files according to your preference but function mymain must reside in pr2.erl
PROGRAM SPECS
input; input; input; done
1
Your program has to follow basic stylistic guidelines, such as proper indentation it is better to use whitespaces to ensure thats the case, meaningful variable names, etc.
You are to save your shell with sample calls to your functions to a file called pr2tests.erl
EXECUTIVE SUMMARY
You are to write an executive summary. It should be written as a txt file. In the file, describe what you have done to complete the assignment in about 500 words and compare your C and Erlang approaches to this program. How has programming paradigm affected your workchoices? Which one do you prefer and why? The word count is not strict, so do not worry about going slightly over; however, summaries that are400 words or are trivial in nature representing little thought or effort will not get full credit.
EXTRA CREDIT
Extend the program in an interesting way or collect stats over multiple runs and add conclusions. If your extra credit results in more code, then you need to submit four files for grading: pr2.erl that contains the assignment, the run of the shell saved into pr2tests.erl, pr2EC.erl that contains the assignment with extra credit, and the shell showing its usage saved as pr2ECtests.erl. At the top of pr2EC.erl explain what your extra credit is.
SUBMISSION AND GRADING NOTES
You are to submit your finished program through Canvas. This is an individual assignmentyou are NOT allowed to work on it with any other student or share your code with others. The code will be graded based on its correctness by running it on instructorgrader designed test cases. Then, the code will be looked over for anything that violates good coding practices or the assignment specs e.g. nonmeaningful variable names, lack of code modularization. Note that you may turn in this assignment 7 days late, with no penalty. However, no submission past this deadline will be accepted even if you submit one minute after the deadlines timestamp7 days of lateness is more than enough.
Grading points will be distributed in the following fashion:Running program
o Directory table operations
o Block table operations
Proper modularization
Coding style and comments
Shell saved as a file
Executive summary
Extra credit
15 pts 15 pts 5 pts 5 pts 5 pts 5 pts 5 pts
2
Reviews
There are no reviews yet.