cs504 GDB (Graded discussion Board) Spring 2012 Today is closing date.

Despite the importance and focus on SE development model in academic, it is a cruel fact that SE model is not deployed in industry practically but with modifications. What are the reasons behind this? Justify your answer with valid arguments.

There are many reasons which tell us about that SE model is successfully adopted in academic but not in industry. There are following reasons which may tell us about this cruel fact.

1.      During testing phases model does not explain or provide a clear picture of problems.

2.      Due to the lack of skills it is not implemented successfully.

3.      It is too time and cost consuming.

4.      Its implementation is very difficult.

5.      Poor model requirements are at a moderate to high risk of changing.

6.      The quality SE model for all needs is difficult to design.

7.      Industrial authors want to add lengthy information and introduction which is not easy to do in a SE model.

8.      Methods used in SE model development are formally based but methods used in industry are rarely formally based, they are well developed and understood. In order to incorporate into industrial practice, formal methods must need the current standard.

9.      The criteria used for the evaluation of SE development model are tended to the vague and ambiguous. They are often derived from author experience from a particular project.

10.  With growing of time, there can be many changes in industrial process which lead to the changes in SE model, so changing in SE model is not an easy task. It is very difficult to make changes in SE model. Which discourage the use of SE development model in industry. 

CS504 GDB Solution & Discussion Last Date:06-07-2012

Dear Students,
This is to inform that Graded Discussion Board (GDB) will be opened on 5^th July, 2012. Below is the topic for GDB. 

Despite the importance and focus on SE development model in academic, it is a cruel fact that SE model is not deployed in industry practically but with modifications. What are the reasons behind this? Justify youranswer with valid arguments.

Note that GDB will remain open for 2 days only (from 5^th July to 6^th July), and no extra time will be given for posting the answer. Therefore, make sure that you submit your answer within the given time.

CS504 Assignment No 5 Solution & Discussion Due Date: 23-01-2012

                        Guideline to avoid un-maintainable code

Unmentionable code:

                                    We all have had experience of modifying the code that one has written, either to add a new feature or fix a problem in a module. The code which is hard to understand and modify by any other programmer is said to be un-maintainable code.

Detail:

            Consider the following example to understand the above statement

Hard to understand code? nY = (nTotal-1)/nX + 1;

Is this code fragment hard for you to understand? If not, then you know the technique being used. If you do not know the technique, then it is sure frustrating to figure out. This code is one way to implement the ceil function on the nTotal/nX value. He views your code through a toilet paper tube. He can only see a tiny piece of your program at a time. You want to make sure he can never get at the big picture from doing that. You want to make it as hard as possible for him to find the code he is looking for. But even more important, you want to make it as awkward as possible for him to safely ignore anything. Programmers are lulled into complacency by conventions. By every once in a while, by subtly violating convention, you force him to read every line of your code with a magnifying glass. Properly commenting your code is a good first step. However, keep in the back of your mind that someone else is reading your code and avoid obscure programming techniques unless they are fully commented and documented in the project. Much of the skill in writing unmentionable code is the art of naming variables and methods. They don't matter at all to the compiler. That gives you huge latitude to use them to befuddle the maintenance programmer.

Guideline to avoid un-maintainable code

1. Lie in the comments. You don’t have to actively lie, just fail to keep comments as up to date with the code.

2. Pepper the code with comments like /* add 1 to i */ however, never document wooly stuff like the overall purpose of the package or method.

3. Make sure that every method does a little bit more (or less) than its name suggests. As a simple example, a method named is Valid(x) should as a side a effect convert x to binary and store the result in a database.

4. Use acronyms to keep the code terse. Real men never define acronyms; they

understand them genetically.

5. In the interests of efficiency, avoid encapsulation. Callers of a method need all the external clues they can get to remind them how the method works inside.

6. If, for example, you were writing an airline reservation system, make sure there are at least 25 places in the code that need to be modified if you were to add another airline. Never document where they are. People who come

7. Never use i for the innermost loop variable. Use anything but. Use i liberally for any other purpose especially for non-int variables. Similarly use n as a loop index.

            References.

1.                http://www.schoolstuff.be/1stelic/software_engineering/Theorie_How_to_write_unmaintable_code.pdf

2.                http://thc.org/root/phun/unmaintain.html

Assignment No. 04 Semester: Spring 2012 CS504: Software Engineering-I

	Assignment No. 04 Semester: Spring 2012 CS504: Software Engineering-I		Total Marks: 20 Due Date: 18/06/2012
Instructions Please read the following instructions carefully before assignment submission. It should be clear that your assignment will not get any credit if: §  The assignment is submitted after due date. §  The submitted assignment does not open or file is corrupt. §  All types of plagiarism are strictly prohibited. Objective The objective of this assignment is: §  To assess your overall understanding of Software Engineering concepts §  To check your level of understanding for Software Architecture §  How we create deployment view of system based on scenario description Note: The assignment should be in .doc format. Assignment in any format other than MS Word format will not be accepted. You are required to recall the concepts related to Unified Modeling Language (UML), Software Architecture and deployment view (Krutchen’s 4+1) before solving this assignment.
Assignment
Description: Consider the Healthcare Sales Management system again, this time you are required to draw a deployment diagram for the scenario given below: Architecture of health care management system consists of two tiers of servers; application server and database server. We have one application server and two database servers. Both database servers are identical; first acts as a main server, while the second acts as a redundant backup in case the first one fails. Clients can access database server through application server. For above system, we also have the option of using a proprietary client that accesses the databases directly. Question: Given the above scenario, you are now required to draw deployment (physical) view based on Krutchen’s 4+1 architectural model for the above system depicting normal client access scenario as well as proprietary client access scenario. You are also required to explain your deployment diagram that how data will flow from client to server and then from server to client (request initiation to reply from server). Explanation of deployment diagram should be done in not more than 4 to 5 lines.

CS504 Software Engineering - I Assignment No 3 Solution Spring 2012

CS504: Software Engineering-I Assignment No. 03 Semester: Spring 2012

	Assignment No. 03 Semester: Spring 2012 CS504: Software Engineering-I		Total Marks: 20 Due Date: 05/06/2012
Instructions Please read the following instructions carefully before assignment submission. It should be clear that your assignment will not get any credit if: §         The assignment is submitted after due date. §         The submitted assignment does not open or file is corrupt. §         All types of plagiarism are strictly prohibited. Objective The objective of this assignment is: §         To assess your overall understanding of Software Engineering concepts §         To check your level of understanding for use cases §         How we create sequence diagram based on use cases Note: The assignment should be in .doc format. Assignment in any format other than MS Word format will not be accepted. You are required to recall the concepts related to Unified Modeling Language (UML), use-cases and sequence diagrams before solving this assignment.
Assignment
In assignment 2, you were asked to develop use-case model and data flow diagram for HealthCare Sale Management System. Continuing further, you are now required to draw sequence diagrams for the some of the use cases identified in previous assignment. Remember that this assignment is based on solution of your previous assignment (Assignment 2). Description: Advance HealthCare is a medicine manufacturer company which manufactures medicines and sells to its customers. Advance HealthCare wants to develop an online system which will facilitate to manage the routine tasks of medicine sales and will convert the manual working in a computerized system. The system is meant to manage almost every aspect of the medicine sale system such as maintaining the stock record of the medicine, suppliers/companies accounts, purchase record, customer (patient) record, sales invoice generation, employees’ record etc. This system will maintain all the sales of medicines to customer and purchase from supplier. The medicine stock will be managed along with their batch numbers, expiry date, rate and quantity. When the medicine is purchased, and record is entered, the stock record will be updated immediately. The system will also handle the accounts including payments to suppliers and receiving from customers. The proper ledgers of every account will be maintained. The system will also help in maintaining the employees’ record that includes storing their name and other particulars along with their salary package. The system will generate many sophisticated reports including stock reports, ledger prints and rate lists. The system will not generate any advanced accounting reports as trial balance, balance sheet, Operating Expense Report and worksheets. The System should be user friendly, technology independent and platform independent. The System service should have availability most of the time in the day. It must be capable of supporting multiple users at a time without affecting the performance. It should be able to complete its on-going operations in spite of any error or problem within defined response time. Question:  You are required to draw Sequence Diagrams for the following two Use Cases: 1)    Add Account   HINT: Using this use case, the manager will be able to add new account into the system. 2)    Update Item   HINT: This use case will allow the user to update the information for an item (medicine) in the inventory.

 ``

CS504 Assignment No 5 Solution & Discussion Due Date: 23-01-2012

Software Engineering-1 (CS504)

Assignment # 5 (Fall 2011)

  Total marks = 20

                                                                                       Deadline Date = 23-01-2012

Please carefully read the following instructions before attempting the assignment.

Rules for Marking

It should be clear that your assignment would not get any credit if:

• The assignment is submitted after due date.
• The submitted assignment does not open or file is corrupt.
• The assignment is copied. Note that strict action would be taken if the submitted assignment is copied from any other student. Both students will be punished severely.

1)      You should concern recommended books to clarify your concepts as handouts are not sufficient.

2)      You are supposed to submit your assignment in .doc format. Any other formats like scan images, PDF, Zip, rar, bmp, docx etc will not be accepted

3)      You are advised to upload your assignment at least two days before Due date.

4)      This assignment file comprises of Two (2) pages.

Important Note: 

Assignment comprises of 20 Marks. Note that no assignment will be accepted after due date via email in any case (whether it is the case of load shedding or emergency electric failure or internet malfunctioning etc.). Hence, refrain from uploading assignment in the last hour of the deadline, and try to upload Solutions at least 02 days before the deadline to avoid inconvenience later on.

For any query please contact: CS504@vu.edu.pk

Question:

An un-maintainable code is one of the candidates that negatively affect overall software maintainability and hence adding to maintenance cost and time.

Search the internet for the term “un-maintainable code” and write down one page article on the following topic:

“Guidelines to avoid un-maintainable code”

Note:

1) Article should be formatted precisely without any grammatical mistake.

2) In case if you need to quote any stuff from other source, then provide proper reference of this source.

Software Engineering-1 (CS504) Assignment # 3 by Virtual University

Software Engineering-1 (CS504)

Assignment # 3

  Total marks = 20

                                                                                       Deadline Date = 26-12-2011

Question:

Keeping in mind the Krutchen’s 4+1 architectural view model, draw a diagram to represent the deployment view (also called physical view) of the above system.

Also explain the diagram with in four to five lines.

Note:

1. Carefully study the 4+1 architectural view model before attempting the assignment.

2. You can use any set of notations to draw the diagram.

3. Explanation should not exceed more than 5 lines.

For any query please contact: CS504@vu.edu.pk

Consider the following case study:

ERP system of Virtual University consists of three subsystems “VIS”, “LMS” and “EXAMS”, all deployed on same web server and sharing a central database (installed on the same web server).

However due to the increased number of students, VU decides to deploy these sub systems on separate web servers named VIS-Server, LMS-Server and EXAMS-Server, still all sharing a central database.

However this time the database will be installed and managed by a separate database server which will be implemented through oracle server.

Now the clients (students and instructors) can connect and request the services from these servers under following protocols:

1)      Students can connect only to LMS-Server and can request services from it.

2)      Instructors can connect with all three servers (i.e. LMS-Server, VIS-Server, and EXAMS-Server) and can request the desired service.

3)      These servers can also connect with each other to get services as when required.

4)      No client i.e. neither the students nor the instructors can directly connect with database server.