DATA DICTIONARY

EXPLODED DIAGRAMS

DOSCST - Science Laboratory Inventory System

JEJ Group

John Carl R. Macaubos

Estella Mae S. Encienzo

Joy Mae F. Ebuetada

USE-CASE DIAGRAM

Use Case: “Search for Meal”

Short Description: “The customer wants to  order foods in the restaurant”

Actor: “Customer”

Requirements: “Customer should have money”

Pre Condition: “The Customer choosing foods in the Menu-List.”

Post Condition: “The Customer successfully ordered his food.”

Main Flow: “The Customer should pay first in the cashier”

Alternate Flow: “The customer's money is not enough to buy this kind of food.”

Exceptions Flow: “Your money is fake!”

Use Case: “Search for book/s”

Short Description: “The student wants to borrow a book in the library”

Actor: “Students”

Requirements: “Each Student should have an ID”

Pre Condition: “ The Student's ID  should already validated”

Post Condition: “The Students may now be able to borrow a book”

Main Flow: “Each Student should present his/her validated ID in the Library Personnel. And records their name, signature, code of the book and the date to a specified record book” 

Alternate Flow: “Your ID was not validate”

Exceptions Flow: “No network connection”

Software Risk

1. What is Risk?

-----Risk is a concept that denotes the precise probability of specific eventualities. Technically, the notion of risk is independent from the notion of value and, as such, eventualities may have both beneficial and adverse consequences. However, in general usage the convention is to focus only on potential negative impact to some characteristic of value that may arise from a future event.
-----Risk can be defined as “the threat or probability that an action or event will adversely or beneficially affect an organisation's ability to achieve its objectives”. In simple terms risk is ‘Uncertainty of Outcome’, either from pursuing a future positive opportunity, or an existing negative threat in trying to achieve a current objective.

Reference: http://en.wikipedia.org/wiki/Risk

2. Identify at least 5 software risk. Discuss each.

a.)Staff Turnover: This kind of software can affect the success or failure of a project since in this situation. the working staff leave before the project is finished, so we can just imagine the scenario when there is staff turnover, so the whole project and the management will be put in "hot water".

b.) The project itself: This kind of software risks include inadequate configuration control, cost overruns and poor quality. Poor quality means the software either does not work very well, or it fails in operation repeatedly. So this is problem once it is encounter.

c.) Commercial software risks: A finished project may have lower user satisfaction. Lower user satisfaction means the product has low quality, functions inadequately, and has complex structures. Users are also displeased by excessive utilization of disk space or other hardware components requirements by the software.

d.) Hardware Unavailability: A kind of sofware risk where the needed hardware specifically needed of a certain project is not available on a certain schedule that is set that it would be use.

e.) Configuring the Project: This simply means that the project might be in jeopardy once the congifure is mistaken and there will be a great need for the project to reconstruct it again.

3. Identify risk management strategies.

The Risk Management Strategies are:

• identify, characterize, and assess threats
• assess the vulnerability of critical assets to specific threats
• determine the risk (i.e. the expected consequences of specific types of attacks on specific assets)
• identify ways to reduce those risks
• prioritize risk reduction measures based on a strategy

Reference: http://en.wikipedia.org/wiki/Risk_management

4. You are asked by your manager to deliver software to a schedule which you know can only be met by asking your project team to work unpaid overtime. All team members have young children. Discuss whether you should accept this demand from your manager or whether you should persuade your team to give their time to the organisation rather that their families. What factors might be significant in your decision?

-----The factor that I should consider would be the availability of time of all my team mates in a project. By asking them, we could have our consultation period & as well changing of comments and suggestions about the said project. As a working team, we should come up with a unified decision. That's why I couldnt say that I could accept the demand without prioritizing first the rights & the status of all the members of the project team. I wont take the risk if I know it will turn out to worst outcome. There's nothing bad about talking personally and sincerely to the manager saying the true reason why we cannot deliver the said project.

5. As an IT student that has been trained for Java Programming, you are offered a home based job as a project manager for a certain software project, but you feel that you can make more effective contribution in a technical specifically doing progamming module using Java for the project rather than a managerial role. Discuss whether you should accept the job.

-----Basically, I will not accept the job. Why? Because how can I work efficiently, effectively, & productively if the task that was assigned to me is not my forte. I cannot give all the knowledge that I know if i will accept something which I know is beyond my limitations. Trying is not bad, but if there's other option to choose, why should we take the road which we think could affect our performance? Try to be wise! Don't just be blind for the position, think more ethically & practically.

HOUSE & LOT

Think of all the task that you perform when you purchase a house & lot. Include any research, decisions considerations, or financial issues that relate to the purchase. Draw a Gantt Chart & PERT Chart that shows all the tasks and the estimated duration of each.

(Note: You should come up with a task listing as well as its dependencies.)

PROCEDURES IN PURCHASING A HOUSE.

1. Get pre-qualified for a loan. (10 days)


2. After the loan pre-qualification you can now talk to a Realtor to show you houses. (5days)


3. You now make an offer. (3days)


4. After analyzing the offer it will now be accepted. (2days)


5. You can open an Escrow. (5days)


6. After opening an Escrow two task can be perform you can make Deposit (3days) & do home inspection. (right after opening escrow) (3days).


7. As part of the home inspection two task again can be perform. You can ask for a copy of termite inspection (1day) & Ask for copy of all Seller's Disclosure and approve them (2days).


8. Review home inspection and ask for repairs.(2days)


9. By this point you are probably about (17 days) after acceptance. Make sure you lender already has the unconditional loan approval and knows you are good to go and it is also part of the process in making a deposit.


10. Once you know you are approved, have seller do termite work. (3days)


11. (5 Days) Prior to close of escrow you will do a "Final Walk Through" to make sure your house is in the same or better conditions as when you wrote the offer and that all of the agreed repairs have been done.


12. Loan will be funded (closed) (14 days).


13. After the loan has been funded the title will be recorded. (escrow is closed) (1day)


14. Usually, seller has (3 days) to vacate the house.


15. Move into your home.(7days)


16. Don't forget to change the utilities under your name.(3days)

Reference: http://smallbusiness.yahoo.com/r-answers-a-20080321152908AAHHpGA-k-escrow+accounts

Software Engineering Assignment No. 2

"SMS Based Student Information Inquiry of DOSCST System"-(PERT CHART)

Task               Description                                       Duration             Dependencies

A                     Send Communication                       1 day                    ---

B                     Develop Training Material               7 days                   A

C                     Training Facilities                                 3 days                   A

D                     Hand-out Material                                 3 days                  B

E                     Set of Electronic Presentation              5 days                B

F                     Conduct Practice Training System      2 days               E      

G                    Conduct Training Session                        2 days              C, D, F

---end---     

IT121-Pert Chart Exercise

Exercise No. 1 

(PERT CHART)

Computer-Aided Software Engineering - (CASE) Tools

1. Computer-Aided Software Engineering (CASE), in the field of Software Engineering is the scientific application of a set of tools and methods to a software which is meant to result in high-quality, defect-free, and maintainable software products.It also refers to methods for the development of information systems together with automated tools that can be used in the software development process.  It can refer also  to the software used for the automated development of systems software, i.e., computer code. The CASE functions include analysis, design, and programming. CASE tools automate methods for designing, documenting, and producing structured computer code in the desired programming language.

              Two key ideas of Computer-aided Software System Engineering (CASE) are:

             the harboring of computer assistance in software development and or software maintenance processes, and
                     An engineering approach to the software development and or maintenance.

          Some typical CASE tools are:

1. Configuration management tools
2. Data modeling tools
3. Model transformation tools
4. Program transformation tools
5. Refactoring tools
6. Source code generation tools, and
7. Unified Modeling Language
   
   Many CASE tools not only output code but also generate other output typical of various systems analysis and design methodologies such as:

1. data flow diagram
2. entity relationship diagram
3. logical schema
4. Program specificatio
5. SSADM.
6. User documentation

2. A CASE tool is a computer-based product aimed at supporting one or more software engineering activities within a software development process.

References: 

1. http://en.wikipedia.org/wiki/Computer-aided_software_engineering

2. http://www.ask.com/bar?q=what+is+CASE+tool%3F&page=1&qsrc=0&ab=1&u=http%3A%2F%2Fwww.sei.cmu.edu%2Flegacy%2Fcase%2Fcase_whatis.html

WHAT IS SOFTWARE ENGINEERING?

1. Software engineering is application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.
2. Software Engineering is an approach to developing software that attempts to treat it as a formal process more like traditional engineering than the craft that many programmers believe it is. We talk of crafting an application, refining and polishing it, as if it were a wooden sculpture, not a series of logic instructions. The problem here is that you cannot engineer art. Programming falls somewhere between an art and a science.The computer science discipline concerned with developing large applications. Software engineering covers not only the technical aspects of building software systems, but also management issues, such as directing programming teams, scheduling, and budgeting.
3. Software engineering (SE) is concerned with developing and maintaining software systems that behave reliably and efficiently, are affordable to develop and maintain, and satisfy all the requirements that customers have defined for them. It is important because of the impact of large, expensive software systems and the role of software in safety-critical applications. It integrates significant mathematics, computer science and practices whose origins are in engineering.

References:

1.  http://en.wikipedia.org/wiki/Software_engineering

2. http://wiki.answers.com/Q/What_is_software_engineering

3. http://computingcareers.acm.org/?page_id=12