CS7140 Spring 2017 Project pdfRenamer Logistics
Table of Contents
Let us name the primary piece of software resulting from this project
as pdfrenamer.
1 Status as of Sat March 18, 2017
1.1 Links
- Apoorva https://github.com/apoorvavinod/AdvancedSoftwareEngineering
- Jayant https://github.com/jayanthanantharaman/AdvanceSoftwareEngineering
- Jonathan https://github.com/MasterGeese/CS7140/tree/master
- Sarker https://github.com/md-k-sarker/PDF-Renamer/
- Stephanie https://github.com/sbelow1/PDFRenamer.git
1.2 Test PDFs
- I asked each of you to contribute 5 test PDFs.
- Done, but they are not all on GitHub. Why not??
- They are not annotated, showing fields of interest.
1.3 Requirements
- Both teams have submitted. Below are the links.
- Jonathan + Sarker
- Apoorva + Jayant + Sarker
1.4 Reviews of Requirements
- Each student reviewed the Req Doc of the other team.
- Five reviews done. Quite "reasonable" reviews.
2 By The Final Week
- Previous Reports: (i) Requirements, (ii) Specifications, (iii) Design, (iv) Implementation, (v) Testing.
- The final report for the project is essentially an assembly of all the previous reports, which now become chapters, revised if necessary. This is the 6th report.
- Crucial are the Final Report, and the demonstrable piece of
software:
pdfrenamer. - All six reports are to be submitted. As I said several times, due dates can be negotiated – but, not beyond the end of term.
3 The Next Few Weeks
- The next milestone is the specification.
- We discussed what Domain Analysis is, and why we do it. For our project, is it clear enough in your thinking? Are you familiar enough with the PDF libraries? Can you name the PDF-extraction-operations mnemonically? Are you ready to rigorously (even without math and logic) specify? If you could, that would make the core of the Spec Doc.
3.1 Specification
- My assessment on Mar 15 was that you are not ready to do Specs. But, I did not say so in class. Instead, I gave a constructive suggestion.
3.2 Suggested Work
- Combine the two Requirements Docs into one, benefiting from the reviews. Also, include domain analysis. Let us call this RDv2. Use RDv2 as the basis for remaining work.
- Intuitive discussion of domain analyses is necessary, but not sufficient. Develop "trial" implementations of the PDF-extraction-operations. This will constitute neither a Spec nor a Design.
- I hope to discuss Test Driven Development (TDD) and Agile Development soon. These are relevant to the above.
- Write a TR documenting the above effort. I did not give a name to this TR. I said [something to the effect that] submit this instead of Specs.
- The due date was Mar 17, which was extended to Mar 18. I am composing this note around 9:00 PM. So, the due date of Mar 18 11:59 PM does not seem feasible. Which is OK. You come up with a due date, and we discuss this quickly on Mar 20. Obviously, the due date of Mar 18 is dropped.