knightbk / junior-project-mobile-student-lookup Goto Github PK

probably has to do with code called in viewDidLoad of SettingsViewController.

Most of the work has been completed and added to the site here, we just need to compile it into a single unified document.

so we can mimic that behavior in our app.

Building on task 1, finalize your analysis and design models. Add any relevant conceptual classes and associations. Recognize that you have moved beyond the logical design, and physical design is quite relevant in this assignment. That is, you should expect to find a number of classes and interactions that are Pure Fabrications or utility classes (e.g., database mappers, webpage observers, device drivers). You may find it useful to do some analysis and design on functionality that will be implemented in the future. If you do that, please carefully note what parts of your models are left for future implementation.

Activity Diagrams

It appears that our error states that credentials are wrong if the problem is with the network connection itself (AKA no network connectivity). We should change this to say "Make sure you have a valid network connection and that your credentials are up to date" or something like that such that you don't get an invalid credentials message when credentials are valid but network is down.

This is required for our acceptance plan for M5.

@knightbk

I stupidly forgot to remove the spaces from the PDF file names. I know you fixed this once before - I couldn't figure it out.

Ann will make the UML Diagram

seems to be only happening to me.

@vitalema sent me this.

Tell the members who have not used git before that we need to name things without spaces. i.e. Milestone_1 instead of Milestone 1.
@vitalema
@knightbk

Update your acceptance test plan from CSSE 371 as necessary based on changes to your analysis and design this term. Use the format that you used for this test plan in 371. This plan will be used for some of the demonstration in task 7. The plan may now be in part an integration and acceptance test plan:

a. Integration tests: We want to go light on the integration part here, because you have limited time left this term, but you may need a little of this. Integration testing is the name for ways to test the interfaces and other ways the parts of your system interact. It is a major part of "white box testing," the part that builds on unit testing. If you are an SE major, you'll see more of this in CSSE 375. We don't want you to go overboard on testing the internals, but please do so when it's necessary to show that partly developed features work. This would be especially true of parts of the system that you cannot see from the GUI. We are not expecting an industry strength integration plan here, but it should serve as a guide for us to watch your demo that shows from the code how the design has been implemented properly.

b. Acceptance tests: These are main tests. They likely will show that everything works from the GUI as the user would operate the system. However, it may also show other things - e.g., if the user needs to verify that the data in the database is correct.

@SparkSovereign
@knightbk

Update your analysis and design models (i.e., Domain Model, System Sequence Diagrams, Operation Contracts, Interaction Diagrams, Logical Architecture, and Design Class Diagrams) from Milestone 4 based on the feedback from your instructor

This is a good tutorial:

http://gitimmersion.com/

Extend your discussion of GRASP principles from Milestone 4 to incorporate GoF patterns. Discuss any of the GoF patterns from Chapter 25 (i.e., Adapter, Factory, Abstract Factory, Strategy, Façade, and Composite) that you applied to arrive at your design. To succeed at this task, you will need to compare your given design to alternatives. After all, the GRASP principles and GoF patterns are all about making decisions. Also, please note where these are done in your design so that we know where to look in the design (never a good thing to have the instructor groping about trying to find where you have done work to be graded ☺).

When coding begins, you'll want documentation separated out:

/
+-- Documentation
|      +-- Milestone_1
|      \-- Milestone_2
\-- StudentLookup.xcodeproj