TUTORIAL 12

Tutorial 12

Since the whole semester we had been talking about how to design good systems and interfaces, this week, week 12, we were discussing the implementation and supprot of these systems that we were discussing throughout the semester. Amongst which, we discussed; the issues related to managing andcoordinating the implementation phase of the SDLC, we also described the main implementation and support activities that are involved with maintaining and implementation of systems.
We coverd how implementation activities occur before system isturned over to users so that we as the designers make sure the system is running properly with no errors or setbacks.We also discussed how implementation consumes more time and resourcesthan other phases of the SDLC.
We also were given a few tips on the exam, how it will be structered and what to llok out for.

Goodbye!

TUTORIAL 11

In this week's lab sessions we we examining on how to design good interfaces by examining bad interfaces and discussing what made them bad interfaces. We used The Way back machine which we found on the www.archive.org website to look at old websites such at the old Monash website and discused on why it was a bad interface because it was really bad. We also looked at another wesite called www.websitesthatsuck.com where the site operator Vincent Flanders talks about poor website designs and what makes them poor. He even embarassed one website so much that it was redesigned into a better website. We looked at numerous websites that were properly designed and discussed why we said they were proper.

TUTORIAL 10

In the week 10 lectures we were being taught about Use case Driven Testing. This involved  Quality assurance in systems development which is about ensuring information system meets minimum quality standards, we talked about testing which is the process of examining a product to determine if any defects exist, types of tests, tests and development phases where we used the IBM process for developing test cases.
We discussed basic flows and the alternative flows, how to use them and looked on how these flows differ.
In the lab session, we looked at domain class diagrams while we used Visual Paradigm to help us in working on the problems we were given.

TUTORIAL 9

Tutorial 9

In week 9, in the lectures we described the key elements of requirement specifications,key elements of a request for proposal, and prirotising the system requirements based on designed scope and thelevel of automation for the new system. We also discussed the strategic decisions that intergrate the application deployment environment and the design approach for the new system amongst evaluating and selecting a development approach based on the needs and resources of the organisation then how to develop a professional presentation of findings to management.

In the lab session, we converted domain model class diagrams and a university enrollment class diagram in to ER models and then data structure diagrams and we made up the attribute details for the diagrams where necessary.

TUTORIAL 8

Tutorial 8

In Week 8 we were given we used class diagrams and use case description to develop robustness diagrams for the use case we were given which was about Receive new book. We then developed first cut sequence diagrams for the use case.
The diagram included the actor and problem domain classes. We then added view view layer classes and data access classes from our diagram.
We also used Visual Paradigm to develop package diagrams showing the classes in a three layer view solution which included view layer, domain layer and data access layer packages. The tutors helped us whenever we had problems drawing the diagrams so it was not that difficult a week.

TUTORIAL 7

Tutorial 7

In week 7, we continued with work on the exercise from week 6 which involved the use of Visual Paradigm for UML. We continued from Use case modeling since we had done Class diagrams in week 6. We started by drawing the Use case model which involved an example of the order entry subsystem.
After that we drew activity diagrams of the telephone order scenario and created sequence diagrams of the same telephone order scenario for the create new order use case. With the help we got from the tutors we managed to draw the diagrams easily using Visual Paradigm.

TUTORIAL 6

Tutorial 6


In week 6 we were introduced to Visual Paradigm for UML which is a design tool and UML CASE tool designed to aid software development and VP-UML supports key industry standards such as Unified Modeling Language (UML) It offers complete toolset software development teams need for requirements capturing, software planning, test planning, class modeling, data modeling, and etc.We spend some type exploring its layout and menus. Since it was the first time working with this software, i took some time to read the online documentation of the product and at the same time i was exploring the software trying what i was learning from the documentation. i started by doing the exercises which involved me redrawing models and once i was acquainted with the software, i left the rest for week 7.

TUTORIAL 5

Tutorial 5

This week we were dealing with usability testing which involved designing and conducting a usability test of a system interface. Therefore in the weekly lab session we created class diagrams from a problem we were given in the lab exercise. The class diagrams we were creating were about a university and the relationships between the university, its professors, lectures, students and academic staff. We also discussed on how to develop event tables that describe the operation of a lift. We listed all the situations that the system needs to respond to, identify the actors involved, the inputs and outputs. We also identified the events which were independent from each other.

TUTORIAL 4

Tutorial 4

This forth week we were focusing on user interface, applying the eight golden rules of dialog design when
designing the user interface principles in order to be able to do the assignment on designing a web user interface.
In our lab session, we were divided into groups in which we were role-playing as the client for the assignment case study. In our group we were asking question which would help us to design the web interface for the assignment. Each assignment lasted about 15 minutes. After the interviews we wrote summaries on how they had gone and started working on the assignment. We then used UML class diagrams and sequence diagrams to
document dialog designs.