Thursday, January 22, 2009

logos v0.1




Wednesday, January 21, 2009

ISS103_6-SA29-AD project

Module Code : ISS103_6
Project Title : SA29-AD project
Lecturers :

Wang Meng-Hsuen, Megan isswangm@nus.edu.sg
Tan Meng Yoke, Esther isstane@nus.edu.sg
Venkat Ramanathan issrv@nus.edu.sg
Chia Yuen Kwan isscyk@nus.edu.sg


Group Name : Team
Project Topic : Project Topics Assigned By Lecturer.
Topic Description : -
Project Type : Group Project
Project Opening Date : Thursday, January 01, 2009 12:00 AM
Project Expiry Date : Sunday, February 15, 2009 12:00 AM

Tuesday, January 20, 2009

Finalizing the required documentations

User Requirement Specification
Functional & Non-functional requirements
Security access table
main task table
Peak time consideration
Hardware needs
Response time
use case diagram & reports
Architecture
Sequence Diagram

WANTED FOR SPYING...




Attention for SA29 members, if you are approached by this person, please notify Michael for immediate action.

Confidential files have been breached and we believe that this person is involved.

You cooperation is greatly appreciated.

Logic University
Security and Defence Department

2nd week project to do list 19th January 2009

2nd week project to do list 19th January 2009


1. Complete analysis sequence and class diagrams.
2. Finalize the win forms.
3. Fill up the database with meaningful data.
4. Complete design sequence and class diagrams for meeting with Esther/Yuen Kwan
5. Coding from Thursday 21st January 2009
6. Integration after 27th January 2009
7. If finished ahead of time, please prepare integration test scripts
8. Follow up incomplete coding.




Project Manager
IT Solution

Database Design V.8 20.1.2009



Changes made to collection and consolidate request ; status

Monday, January 19, 2009

Some tips for the team

This is a little story about four people named Everybody, Somebody, Anybody, and Nobody.

There was an important job to be done and Everybody was sure that Somebody would do it.

Anybody could have done it, but Nobody did it.

Somebody got angry about that because it was Everybody's job.

Everybody thought that Anybody could do it, but Nobody realized that Everybody wouldn't do it.

It ended up that Everybody blamed Somebody when Nobody did what Anybody could have done

Don't leave ISS without IT ...

Fail to plan, plan to fail ...

There is no great achievement that is not the result of patient working and waiting.
J. G. Holland


High achievement always takes place in the framework of high expectation.
Jack Kinder

Great things are not done by impulse, but by a series of small things brought together.
Vincent Van Gogh


Most of the important things in the world have been accomplished by people who have kept on trying when there seemed to be no hope at all.
Dale Carnegie

"There is no substitute for hard work."
Thomas Edison

"I never did anything worth doing by accident,
nor did any of my inventions come by accident; they came by work."
Thomas Edison

If you aren't going all the way, why go at all?
Joe Namath


"Many hands make light work. "
~ John Heywood

"Coming together is a beginning.
Keeping together is progress.
Working together is success. "
~ Henry Ford

"Teamwork divides the task and multiplies the success. "
~ Unknown

"Talent wins games, but teamwork and intelligence wins championships. "
~ Michael Jordan

"It is amazing how much you can accomplish when it doesn't matter who gets the credit. "
~ Unknown

"Contrary to popular belief, there most certainly is an "I" in "team." It is the same "I" that appears three times in "responsibility." "
~ Amber Harding
javascript:void(0)
"If a team is to reach its potential, each player must be willing to subordinate his personal goals to the good of the team."
~ Bud Wilkinson

"None of us is as smart as all of us. "
~ Ken Blanchard

"Alone we can do so little; together we can do so much."
~ Helen Keller

"Yes, we can" - Obama

Workflow Status Flag

Request Type

Normal

Largeamount

Lowstock

PendingApp

PendingApp

Submitted/Rejected

Submitted/Rejected

Lowstock

processing

Processing

Processing

POSubmited

POSubmited

WaitingDelivery

WaitingDelivery

Retrieved

Received

Received

Collected

Collected

Distributed

Distributed

National University of Singapore (NUS ), School of Computing

Graduate Diploma in Systems Analysis (GDipSA)

NUS ISS Exam Preparation for all Science Graduates (especially for non-IT background)


Aptitude Test
All GDipSA applicants are required to sit for the aptitude test. This is a test to measure your aptitudes for learning and performing the job of computer programming and systems analysis. There are four parts to the test and each part will be timed separately - Verbal Meaning, Reasoning, Number Ability, and Diagram Ability. It is designed to test your problem-solving ability, your ability to read and understand diagrams, etc. You can't really study for the test. It is designed to test what abilities you have, as opposed to testing what facts or information you know.

Sample Questions
Verbal Meaning
Each item in this part of the test presents a word, followed by five alternatives. You are to choose from the five words the one that means the same or most nearly the same as the word at the beginning.
Sample question: Recipient
1. donor 2. owner 3. performer 4. receiver 5. borrower
Answer: the word recipient means the same as receiver.

Reasoning
This is a test of your ability to reason and to express problems in a simple form using conventional mathematical symbols. The items in the test require you to read a problem and formulate an answer for it. Sample question: An office manager ordered a conference table which cost S dollars, a dozen chairs which cost P dollars each, and three book shelves which cost Y dollars a piece. The total cost of the order in dollars is
1. S + P + Y
2. SP + 3Y
3. S + 12P + 3Y
4. S + (P + Y) / 4
5. S + P +3Y
Answer: 3

Number Ability
This test measures your ability to make rapid numerical calculations and estimates.
Sample question: (123 / 11) + 18 (approximate)
a) 15 b) 27 c) 30 d) 33
Answer: c

Diagramming
In this section there are a number of problems with flow charts (schematic diagrams) that illustrate the process by which each problem is solved. The solution to a problem is illustrated in its diagram by following the arrows from cell to cell.
Sample question:
See the Diagram at http://zmagmdy.googlepages.com/ISSSample.JPG

Problem and Conditions
A. A company inspects and classifies its products in lots of 100.
B. It is necessary to classify the individual pieces within each lot of 100 into three classes by weight:
Class K – 4.5 oz. or over
Class L – 3.5 to 4.4 oz.
Class M – less than 3.5 oz.

Cell 1.
A. Is it less than 3.5 oz.?
B. Select a piece.
C. Is it 3.5 to 4.4 oz.? YCLASSIFY AS K CLASSIFY AS L2 INCREASE COUNT BY 1IS COUNT 100 Y N 3 Y
D. Classify as M.
E. Classify as L.
Answer: C.

Cell 2.
A. Classify as K.
B. Classification of lot complete.
C. Select a piece.
D. Classify as M.
E. Classify as L.
Answer: D.

Cell 3.
A. Select a piece.
B. Classification of lot complete.
C. Classify lot as K.
D. Classify lot as L.
E. Classify lot as M.
Answer: B.

Another of mine...the same tho

click here

Welcome to the unofficial guide to ISS NUS

Welcome to my guide to Institute of System Science, National University of Singapore (afterwards referred to as ISS, NUS respectively).

Its an unofficial insight into the infamous ISS. The following log will include pictures, biographies, stories, tragedies, triumphs...in short..the agony and ...nice experience surprisingly. Not forgetting the occassional rants. ;-)

Let not this be your cautionary tale nor your ONLY guide to survive the SA course.

God Bless,

Peter
Institute of System Science
National University of Singapore.