Ty Bsc Computer Science | Scheduling (Computing) | Thread (Computing)

University of Mumbai

T.Y B. Sc. (Computer Science)

Syllabus

(W.E.F. 2005-2006)

________________________________________________________________________ Prop. Syllabus Page 1 of 29 T.Y.B.Sc. Comp.Sc. Jan 2005

(T.Y. B. Sc. Computer Science Syllabus) There are Six Units in each paper. If there are two sections, each section of the paper is divided in 3 Units. The detailed references are mentioned at the end of each section instead of merely giving a list of reference book at the end of the paper. It is expected that the question paper will have twelve questions, two in each unit, with internal option. The student will be required to attempt six questions, one in each unit. Thus the study of any unit in the paper may not be left as an option. 1. Syllabus details gives a list of practicals, with minimum number of practicals to be performed. 2. For the purpose of examination, the breakup of total marks for practicals (200 for Group I to IV and 80 for Applied Component) will be as follows: A) Main subject Practical Examination: Experiment I (Group I Practical) : 45 Marks Experiment II (Group II Practical) : 45 Marks Experiment III (Group III Practical): 45 Marks. Experiment IV (Group IV Practical -PROJECT ): 50 Marks. Journal(Group I to III) & Viva-voce on Journal : 15 Marks. ------------Total 200 Marks. ------------B) Applied Component Practical Examination: Experiment I : 35 Marks. Experiment II: 35* Marks. Journal & Viva-voce on Journal : 10 Marks. --------------Total 80 Marks. Expt. II examination will be in the form of demonstration and Viva-voce on project, as mentioned in the syllabus. Each student must maintain a record of the experiments & projects performed, as per the syllabus and must bring the certified journals and project reports, duly signed by the teacher concerned and the Head of the Dept. at the time of final examination.

Note: (a)

(b)

3. Requirement of the batch size, number of students per computer in a batch and the network configuration and other details are same as mentioned in Annexure III of the earlier report of the committee. 4. As regards the lab requirement (Hardware & Software), space and time table requirements are satisfied; the colleges may have multiple batches at T.Y.B.Sc. (Computer Science) Class. 5. The Bachelor of Science (B.Sc.) with Computer Science course has the status, as one of the subject at the B.Sc. Course. It is further clarified that adequate laboratory staff (viz. Lab. Assistant and Lab attendant) are required for conduct of B.Sc. Computer Science Practicals, on the same pattern as with the other science subjects such as Physics, Chemistry etc. For smooth conduct of practicals at F.Y., S.Y. & T.Y.B.Sc.(Computer Science), a minimum of 1 Lab. Asst. and a minimum of 1 Lab. attendant be provided for each lab, each session, during entire period of laboratory practical session.

________________________________________________________________________ Prop. Syllabus Page 2 of 29 T.Y.B.Sc. Comp.Sc. Jan 2005

(Computer Science.C) 40 Group II (A. Group II practicals (of six unit course) will form the course contents.Y. Paper I & Paper II (of six units) and Group I. Comp.Sc.T. B.Y. revised) Scheme Subject title No. .B.Y. Sc. following will be the course structure.B. ________________________________________________________________________ Prop.C) 40 100 PAPER – II 50 60 100 NOTE : For students offering “3 units” of computer science at T.Sc.Sc. Syllabus Page 3 of 29 T. of Theory Practical Lectures Marks Marks PAPER I Section I Section II PAPER II Section I Section II PAPER – III Section I Section II PAPER – IV Section I Section II Systems Software 48 Data Communications 52 and Networking Advanced JAVA VISUAL C++ Operating Systems UNIX 52 48 52 48 100 Group I 50 Total Marks 150 100 Group II 50 Group III 50 Group IV 50 150 100 150 Structured System 52 analysis and Design Object oriented analysis and design and Software 48 testing WEB Design and Technologies and .NET Technologies WEB WEB 50 100 150 Applied Component PAPER I 60 Group I (A.NET Technologies Principles of Design and Technologies.. Jan 2005 .

Arithmetic statements. Language Processing Activities.Recognizing Basic Elements. User Interfaces Unit References Code: DMD (Ch 4. Interrupts. Self-Relocating Programs. Jan 2005 .Macro Definition and Call.B. 8) UNIT III Compilers Statement of Problem . Static. Design of a Two Pass Assembler. Recognizing Syntactic Units and Interpreting Meaning. Design of a Macro Preprocessor Linkers .Search Data structures. Syllabus Page 4 of 29 T.Introduction. Non-local Go To’s. General Model of the Compiler Phases of the Compiler .Y. Passes of the Compiler Data structures . Allocation Data Structures Scanning & Parsing Unit References Code: DMD (Ch 1.Sc. DMD: Systems Programming & OS by D. 2. Interpreters .Software Tools for Program Development. Code Generation. Syntax Phase. Debug Monitors. Interpretation Phase. Editors. Macro Expansion. Pure & Impure Interpreters Unit References Code: For Compilers: JD: Chapter 8. Block structure. Design of a Linker. Pointers. Assembly Phase.Sc. A Simple Assembly Scheme. Automatic.Y.Lexical Phase. Fundamentals of Language Processing & Language Specification. 2.Introduction. Advanced Macro Facilities. Section I CLASS: B. Non-Arithmetic statements.Sc.Relocation and Linking Concepts. Optimization (Machineindependent). COMPUTER SCIENCE SYLLABUS (Revised) Paper I. Storage Assignment.Use & Overview. Storage Allocation. 7.Elements of Assembly Language Programming. Code: For Interpreters: DMD: Chapter 6. External Control & Based Storage Implementation.B. Intermediate form. ********* ________________________________________________________________________ Prop. Call & Return Statements.T. Storage Classes. Recursion. Optimization (Machine Dependent). 3) Unit II Assemblers . Main References: 1. Nested Macro Calls. Additional Ref: DMD: Chapter 6. Language Processor Development Tools Data Structures for Language Processing . Code Generation. A single pass Assembler for IBM PC Macros and Macro Processors . Optimization. JD: Systems Programming by John Donovan TMH. Linking for Overlays. Implementation.M. Pass Structure of Assemblers. Programming Environments. 5. Assembly Phase. Sc (Computer Science) Year III SUBJECT: Systems Software: Paper I Section I Data Communication and Networking: Paper I Section II Periods per week Lecture 4 (1 Period = 50 minutes) Practical -Hours 3 Marks 100 -- Evaluation System Theory Examination Practical per year -- SYSTEMS SOFTWARE Unit I Language Processors . A Linker for MS-DOS.DHAMDHERE (2nd Revised Edition) TMH. Loaders Software Tools . Comp. Non-executable statements.

Distribution of Name Space. Modulation of Analog Signals Multiplexing – FDM.ARP. Digital Signals. DNS in the Internet Electronic Mail (SMTP) and FTP HTTP and WWW Unit References Network Layer: Code: DCN (Ch 19-21) Transport Layer: Code: DCN (Ch 22) Application Layer: Code: DCN (Ch 25-27) Main ref: i) DCN . Syllabus Page 5 of 29 T. Jan 2005 .PAPER-I SECTION-II Data Communication and Networking Unit IV (18) Introduction . Sampling.Internetworks. Addressing.Y. Multicast Routing. Detection. Ipv4. Unicast Routing Protocol.Sc. Data Rate Limits. Fast Ethernet. Transmission Mode Analog Transmission – Modulation of Digital Signal. Domain Name Space.Data Communication and Networking by Behrouz Forouzan (3rd ed) ii) CN . 16) Unit VI Network Layer (16) Host-to-Host Delivery . Protocols (OSI. TCP Application Layer DNS – Name Space. Stop-And-Wait ARQ. Comp. Networks (LAN.B. Selective Repeat ARQ.Sc. Multicast Routing Protocol Transport Layer Process-to-Process Delivery – UDP. Channelization Local Area Networks: Ethernet – Traditional Ethernet. Analog versus Digital.Computer Networks by Andrew S Tanenbaum (PHI) Additional References: i) Local area Networks by Keiser G E (TMH) ii) Data and computer communication by William Stallings PHI (5th ed) ********* ________________________________________________________________________ Prop. TDM Transmission Media – Guided Media. TCP/IP) Physical Layer Signals – Analog Signals. Go-Back-N ARQ. WDM. Unguided Media Circuit Switching and Telephone Networks Unit References Introduction: Code: CN (Ch 1) Physical Layer: Code: DCN (Ch3-8) Unit V Data Link Layer (16) Error Detection and Correction – Types of Errors. MAN. Transmission Impairment Digital Transmission – Line Coding. Error Correction Data Link Control and Protocols – Flow and Error Control. Controlled Access. Routing Network Layer Protocol .Data Communication. WAN). Block Coding. PPP Stack Multiple Access – Random Access. Gigabit Ethernet Connecting LANs – Connecting Devices Unit References Data Link Layer: Code: DCN (Ch 10-14. HDLC Point-to-Point Access: PPP – Point-to-Point Protocol. and Ipv6 Routing Protocols – Unicast Routing.

Component Listener.loading database drivers. Writing servlets. Container Listener. BoxLayout. Understanding the http protocol.B.Implementing Listeners for Commonly Handled Events ( Action Listener. Datagrams-What Is a Datagram?. Tabbed Panes. JSP . Connecting to a URL. Broadcasting to Multiple Recipients Swing Features and Concepts Using Swing Components-The JComponent Class. Combo Boxes. issuing dynamic SQL statements. The Beans Development Kit Using the BeanBox . Writing the Server Side of a Socket. Check Boxes. I & Gr. I & Gr.Server processing of JSP's. Labels. Trees) Laying Out Components Within a Container-Using Layout Managers (BorderLayout. Sc (Computer Science) SUBJECT: Advanced Java: Paper II Section I Visual C++: Paper II Section II Periods per week Lecture (1 Period = 50 minutes) Practical Year III 4 8 (Gr. Bean Customization.Simple Properties. The BeanInfo Interface. III) Hours 3 Marks 100 100 Evaluation System Theory Examination Practical per year 3+3 (Gr. Syllabus Page 6 of 29 T. Indexed Properties Manipulating Events in the BeanBox. Reading Directly from a URL. Menus. processing a ResultSet ________________________________________________________________________ Prop. Java programs in JSP's. Bean Persistence. Using the BeanContext API Unit References Code: J2CR (Ch 25) Code: JPAT (Ch 15) Unit III Java Server side programming – Servlets.Starting and Using the BeanBox. Jan 2005 . III) Paper II Section I Advanced Java Unit I Overview of Networking-Networking Basics Working with URLs-What Is a URL?. Focus Listener. 26) Code: JPAT (Ch 13. CardLayout.CLASS: B. Using Top-Level Containers (Frames.Sc. Servlet API. Root Panes) Using Atomic Components (Buttons. Creating a URL. Lists. Window Listener) Unit References: Code: J2CR (Ch 18. Key Listener. Text Components. Scroll Panes. Mouse-Motion Listener. GridBagLayout) Writing Event Listeners . Mouse Listener. Reading from and Writing to a URLConnection. Applets). 16) Unit II JavaBeans Concepts and the Beans Development Kit . and Radio Buttons. Item Listener. Dialogs. Sockets-What Is a Socket?.Sc. Internal Frames. The BeanBox Menus. GridLayout. Internal Frame Listener. Using the BeanBox to Generate Applets Writing a Simple Bean Properties . JDBC API . establishing a database connection. Bound Properties. 20. Comp. Reading from and Writing to a Socket. Writing servlets to receive requests and send responses.JavaBeans Concepts. Tables. FlowLayout.Y. Applying MVC principles using JSP's and JavaBeans. Writing a Datagram Client and Server. Split Panes. Layered Panes. Using Intermediate Swing Containers (Panels. Constrained Properties. Parsing a URL.

Code: J2CR. Joe Wigglesworth and Paula Lumby. ********* ________________________________________________________________________ Prop.Sc. Course Technology (Thomson Learning). Syllabus Page 7 of 29 T. Java 2 .Y. (1999). Patrick Naughton and Herbert Schildt. Java Programming Advanced Topics. (2000). 2.Sc.The Complete Reference 3/e. Comp. Jan 2005 .Unit References Code: JPAT (Ch 17) Code: J2CR (Ch 27) Main References 1.B. Code: JPAT. TMH.

SDI and MDI Applications.3.31). Document Templates.Device Contexts. Application Frameworks.16. Dialog Data Transfer. 10.Ch-6 ) Unit V Writing Text and Drawing Graphics . Idle Time Processing. Managing Projects. Tool tips.Command Messages. CGdiObject Class: CPaintDC. Developer Studio Resource. Editors. Controls as Child Windows. Kanetkar (BPB) Code: PM: The Complete Reference VC++ .Ch. George Shepherd. 11.17. Main References: Code: YK: Visual C++ Programming – Y.4) Code: PM (Part IV) Code: YK(Ch-1. 12. Comp. and Scot Wingo (WP). Status Bars Document/View Architecture .Sc. Event-Driven Programming.14) Code: PSW(Part V: Ch. Designing Dialogs with Dialog Editor. Keyboard (Keyboard Massage Handlers) Unit References: Code: PM(Part-1-Ch. Visual C++ Compiler: Compiling and Linking. Update Command UI Messages.3. CClientDC. CDialog Class and Programming a Modal Dialog.Paper II Section II Visual C++ Programming Unit IV Introduction to Visual C++: Visual C++ Development Environment (IDE). CWinApp and CFrameWnd Classes. Resources in Windows Programs. serializing an object. Using Class Wizard. Syllabus Page 8 of 29 T.Pappas. Jan 2005 . 13) Code: PSW (Ch. Visual Studio.Y.B. Kruglinski. CMetaFileDC Menus and Resources – The CMenu Class.Sc. Debugging Introduction to Windows Programming and MFC – Windows Basics: Structure of Windows Programs.David J.4. String Tables. Resources and Controls.Modal and Modeless Dialog Boxes. Unit References Code: YK (Ch.Serialization: Making a serializable class.Ch. Common controls.2. ________________________________________________________________________ Prop. Invalidating the Client Area.Using AppWizard. MFC Control Bar Classes.1. CRecordView and CDatabase Unit References Code: YK(8.9. Document and View Classes. Document/View Program Structure File I/O and Database management . The windows Common Dialogs. Keyboard Accelerators Controls and Dialogs . Class Hierarchy of the MFC Library. Menus and Command Messages. Windows Messages Message Maps User Input in Windows – Mouse (Client area and Non-client area Mouse Messages). The MFC ODBC Classes-CRecordSet.13) Unit VI Toolbars and Status Bars .Ch. CWindowDC. Toolbars.Ch-5. GDI Object Creation and Cleanup. Using ClassWizard. Murray (TMH) Code: KSW: Programming VC++ .

Need for Mutual Exclusion. Classifying process interactions. Secondary storage Management. scheduling queues.Y. Main memory Management. Dinning-Philosophers Problem and its solutions (Arrange student’s seminars on the classical problems) Problems arising due to process concurrency: Deadlock and starvation ________________________________________________________________________ Prop. multithreaded models. (WS: Ch 3) Unit II Process Synchronization: General structure of a typical process. Binary semaphores. context switching. processes & resources. Cooperation among the processes.Sc. Need for Process switching. Creation of threads Maximizing CPU utilization: Process scheduling. File Management. UNIX. scheduler: short term and long-term scheduler. CPU scheduling. Clustered Systems. message passing: their use & implementation for mutual exclusion. Classical Problems of Process synchronization: Producer-Consumer problem for infinite and bounded buffers and its bounded buffer solution using semaphore. (SG: Ch3) Process Management: What is a Process?. Sc (Computer Science) Year III SUBJECT: Operating System : Paper III Section I System Study and Unix System Programming: Paper III Section II Periods per week Lecture 4 (1 Period = 50 minutes) Practical 4 (Gr II) Hours 3 Marks 100 50 Evaluation System Theory Examination Practical per year 3 (Gr II) Paper-III Section-I Operating Systems Unit I Introduction: What is an Operating System? Types of Operating System: Evolution of OS Os for Main frame Computer Systems: Batch Systems.B. Jan 2005 .Sc. process control block and its role. 2000. Threading issues. Interprocess Communication: Direct & indirect communication. Kernel based approach OS design issues. monitor and messages Reader-writer problem and its solutions with readers’ priority and writers’ priority. message passing. synchronization. Light weight processes: threads. process synchronization. Operating System Services. Tools for process synchronization: Semaphores. (SG: Ch 4. Termination. Time-sharing Systems. Two and multiple process solutions. Process states: two state and five state model. Multiprogrammed Systems. monitors. Comp. process description. Real time OS Examples of OS including MS DOS. Command Interpreter: interface between user and OS. Critical Section Problem and its solutions. XP) (SG: Ch. OS for Multiprocessor Systems: What is multitasking? Distributed Systems: Client Server & Peer-to-Peer Systems. LINUX and WINDOWS (NT.CLASS: B.1) Operating System structure: Components of OS: Process Management. buffering. 5). OS structure: Layered approach. Syllabus Page 9 of 29 T. concurrent processes. I/O Management. achieving mutual exclusion: Dekker’s Algorithm. What is multiprogramming? Importance of Multiprogramming. Operation on processes: Creation. single & multithreaded processes. Peterson’s Algorithm and their final correct solution for two processes. System calls: Types of system calls System programs: Different categories of system programmes. queuing diagram. user and kernel threads.

other. resource allocation graph.Characterization of deadlock: conditions. I/O System: Overview. Free space management. demand paging. replacement algorithms. structure. Application I/O Interface. Examples related to finding turnaround time.8).I/O burst cycle. 12. 14) ******* ________________________________________________________________________ Prop. Paging. File system implementations. Segmentation. Jan 2005 . Examples related to disk arm movement. Comp. Virtual memory: Background. operations. Swapping.Y. CPU Scheduling: Basic concepts: CPU. resource allocation algorithm. interrupts. 11.Sc. SCAN. Deadlock avoidance: safe and unsafe state. Thrashing: its cause and limiting its effect. 13. Directory implementations. Recovery from deadlock.B. SSTF. waiting time for a given set of processes. Syllabus Page 10 of 29 T. direct. C-SCAN. File access methods: sequential. Deadlock detection. process creation. File system structures. File System: File Concept: attributes. Methods of handling deadlocks. polling. Preemptive scheduling. Page replacement: Basic scheme.Sc. ( SG: Ch 9. scheduler. Allocation methods. I/O hardware: typical bus structure. Scheduling Algorithms.5) Unit III Memory management: Background. Deadlock prevention. Evaluation criteria for scheduling algorithms. (WS: Ch 4. Different directory structure.7. Scheduling criteria. Banker’s algorithm. Examples: Given a snapshot of a system check whether system is in a safe state. 10. Unit References: (SG: Ch 6. Dispatcher. types. Segmentation with paging. direct memory access. Disk Scheduling: FCFS. Contiguous memory allocation.

init Run levels.26) (YK: related chapters) Main References: Section I 1. Operations. File subsystem. tar. (PHI). other commands and statements: if…. File descriptor. System structure. Galvin. Kernel. Characteristic of good password. Jan 2005 . Shell meta characters and their execution. Shell programming: Writing and executing Shell script. looping statements.22 other chapters) (WS: Chapters. handling DOS. elif. creating a file system. adding a hard disk. System calls. logging in and logging out of the system. Code:JM:UNIX made easy by John Muster ( TMH) ________________________________________________________________________ Prop. File Descriptor table. C Shell program. file system mounting. Simple filters. Navigating file system.PAPER-III SECTION-II SYSTEM STUDY AND UNIX SYSTEM PROGRAMMING Unit IV OS Case studies: Overview of WINDOWS (NT.then…fi.) (Arrange student’s seminars on the Example Systems) (SG: Ch 20. Process table. block addressing scheme. UNIX Shell Programming: Shell variables and key words. Managing the terminals. deleting. logging in and logging out as a root.I: Accessing the system using Graphical User Interface. assisting and managing users. 18. Find. Silberschatz. backups.Y.B. read and echo command. 3) Working in UNIX/LINUX part . Monitoring system usage. I/O redirection and piping. Comp. Code SD:UNIX System and concepts ( latest edition ). File System &management: System directories. TCP/IP Networking and Internet: Basic features. partitions: fdisk. Inode. XP) and detailed study of UNIX and LINUX in particular (History. cu.(YK: related chapters) Unit V Working in UNIX/LINUX part . File ownership and groups. General-purpose utilities. g++. Syllabus Page 11 of 29 T. ftp. Creating. UNIX C/ C++ Programming Introduction to compilers gcc. The vi Editor and its environment. Files permissions. Mode of execution. Links to the file. (SD: Ch15) (YK: related chapters) Unit VI Advanced filters: Working with sed and awk (SD: Ch20) (YK: related chapters) UNIX System Administration-I: System administrator. Semaphores. The Shell. Pipes. Memory management. File table. Shell. directory tree structure. r-utilities. Mounting of floppies and CDROMS. Directory permissions. by Sumitabha Das ( TMH) 4. (SD: Ch13. printers. Privileges. Handling Ordinary files. processes management: Process.Sc. I/O System and management. Compiling and Executing C/C++ – programs on UNIX platform. nested if…. copy input-output. addresses and addressing system. Unit References (SD: Ch17. designing principles.II: The processes. threads. dd. uucp. Type of the System: Multi-user and multitasking. data blocks.16) (YK: related chapters) Security in Unix: Password. Section II: 3. checking of file system.21.19. Code:WS: Operating Systems (Second Edition) by William Stallings.Sc. telnet. UNIX System Administration-II: Understanding the file system. Basic file attributes. More file attributes. which describes the example Systems)( YK: Ch1. Inode table.else…. Features of UNIX/LINUX: normal user and super user. test. Understanding UNIX/ LINUX commands. Child process. 14. Code:SG: Opearting System Concepts.25. adding a file system. (SD: Ch1 to12). Startup and shutdown: init. 2000. Code:YK: UNIX Shell programming by Yashwant Kanetkar (BPB) 5. Communication between the systems. Regular expressions and the grep family. Ensuring system security. Gange (sixth edition) 2.

Additional References: Operating Systems Design and Implementation. (Prentice Hall) ********** ________________________________________________________________________ Prop. WINDOWS NT : Achyut S Godbole. R.Groff & P. Jan 2005 .Y.B. Albert S Woodhull. (Prentice-Hall) Operating Systems with case studies in UNIX NETWARE. Weinberg (BPB) The UNIX Programming environment . Comp. Andrew S Tanenbaum. (BPB) UNIX – The Complete Book. (TMH) Working with Unix by Vijay Mukhi . Pike rob & Kerningham Brain W.N. Syllabus Page 12 of 29 T. A guide for professional Users (Galgotia) Understanding Unix – A conceptual Guide.Sc.Sc.

Level of abstraction. 2. Syllabus Page 13 of 29 T.3). forms and files. 2.operational. System Development Projects and the SDLC -The Systems Development Life Cycle.Waterfall Model.the purpose. economic. Code: SEPA. Physical and Logical DFD. Scheduling the project phases Software Development Life Cycle Models . data flow. the Entity-Relationship diagram Process Modeling . roles. Spiral Model.Designing the system flowchart and the system level structure chart. weaknesses and differences between them.4.Determining the automation system boundary Software Design .The general systems approach to problem solving. and locations Data Modeling . identifying system requirements (Sampling documents. ________________________________________________________________________ Prop. Context diagram. 4. strengths. The event-partitioned system model. The concept of data dictionary. Incremental Model. (Ch. devices. Component Based Model. RAD Model. tight English and pseudocode. – Their features. Modeling system requirements for events. 3. (Ch. Code: SADCW.5. Code: SADM. 12). (Ch.Sc.CLASS: B. Process. DFD fragments. 2.Y. organizational units. Code: SEPA.B. Transaction analysis and transform analysis. Site visits. 2. 2. The sources of system requirements. technical. Sc (Computer Science) SUBJECT: SSAD: Paper IV Section I OOAD and Software Testing: Paper IV Section II Periods per week Lecture (1 Period = 50 minutes) Practical Year III 4 4 Hours 3 Marks 100 50 Evaluation System Theory Examination Practical per year 4 Paper IV Section I Structured Systems Analysis & Design Unit I What is a System? .The Structured approach. Unit III Application Architecture Design .Functional and Technical Requirements. Defining project costs and project benefits. Cost/Benefit Analysis for a project – Net present value. Jan 2005 . Module B). type and overview of models. organizational and cultural feasibility. Unit References: 1. Unit II Investigating System Requirements . (Ch. Concurrent Development Model. Evaluating DFD quality. their usage and differences Unit References: 1. 5). payback period and return on investment computations. Interviewing techniques). Code: SADCW. Top level DFD. Decomposing processes. (Ch. structured walkthroughs Modeling System Requirements . (Ch. Comp. Code: SSAIT. Documenting DFD components. Observation of Work environment.11). Modeling system requirement for objects. Questionnaire formulation. structured English. data store.building decision tables. the Object Oriented Approach and the Information Engineering Approach.6). Formal Methods Model and Fourth Generation Techniques.Sc. The three approaches to software systems development . decision trees.Data entities attributes and relationships. 3. Prototyping Model. The First four phases of SDLC.Developing Data Flow Diagrams. data elements descriptions Representing Process Logic . Project Feasibility Study .

Databases and DBMS Designing Relational DBMS’s.Y. 2. 9.B. Unit References: 1. Normal forms upto 3rd normal form. Code: SEPA. (Ch. Representing entities. Designing system inputs outputs and controls Designing the user interface .12).Sc.Sc. (Ch. Jan 2005 .Interface design guidelines. Dialog design. Code: SADCW. Comp.Designing Databases . 13.10. Designing Windows forms. enforcing integrity constraints and business rules.11. relationships. Syllabus Page 14 of 29 T.15). ________________________________________________________________________ Prop.

Instant UML. (2000). Systems Analysis and Design in a Changing World. 2. Unit V Software Testing Techniques – Software Testing Fundamentals. 2. Package diagram Object Oriented Databases . Code: SADCW. Interclass Test Case Design Unit Reference: Code: SEPA (Ch 23) Main References: 1. Code: UMLN. Syllabus Page 15 of 29 T. Whitten and Bentley – Tata McGraw Hill (1998). Pressman – McGraw-Hill International Edition (2001). Additional References: 1. representing classes and relationships Hybrid Object-Relational Databases .Designing object databases.Thomson Learning/Course Technology. Sinan Si Alhir – Wrox/SPD (1998). Test Case Design for Object Oriented Software. Structured Systems Analysis: Tools and Techniques. Architectures. Control Structure Testing. 7. 3. Black Box Testing. Comp. Pierre-Alain Muller – Wrox/SPD (1997). class diagrams.18) Unit VI Object Oriented Testing – Testing OOA and OOD Models.Sc. Unit Testing. Gane and Sarson – Prentiss Hall (1979). Basic Path Testing. the Case diagrams. state transitions and state chart diagrams. object diagrams. 4.10). 9. Testing Methods Applicable at the Class Level. Roger S.B. Satzinger. Integration Testing. System Testing Unit References: Code: SEPA (Ch 17. Code: IUML.Paper IV Section II Object Oriented Systems Analysis Design & Software Testing Unit IV Object Oriented Requirements Specifications and Analysis . component diagrams. Designing the Application Architecture-The Object Oriented Approach . Code: SEPA. (Ch. Object Oriented Testing Strategies. Code: IUML. deployment diagrams. Validation Testing. Code: SADM. Code: SSATT. Relationships. ________________________________________________________________________ Prop. Code: SADCW. Relational DBMS and object DBMS data types Unit References: 1.Y. Software Engineering – A Practitioner’s Approach 5/e. UML in a Nutshell. Jan 2005 . Jackson and Burd .Classes and attributes. 2. states. (Ch. and Applications Software Testing Strategies – A Strategic Approach to Software Testing. 3).Sc.the Unified Modeling Language. Collaboration and sequence diagrams. White Box Testing. Systems Analysis and Design Methods.activity diagrams. Testing for Specialized Environments.

and FlavourPanel. JTextArea. 7.Y. JCheckBox. Classes should be properly encapsulated. Java theory and practicals. 4.Y. 5.3. 4 Define a class that enables the drawing of freehand lines on a screen through mouse clicking and dragging. Additionally the class should display the request method.x or compatible system.sun. The errors could be syntactic as well as logical. Define a test class to demonstrate the program. CitiesPanel: Names of cities inside it. the input data (where it exists). JCombobox.B. and FlavourPanel.3 should not be used in programs. length. which makes the Panel visible. the practicals are not to be treated as a subset of the theory. debugging. Jan 2005 . Further build a server application that receives the sent datagram and prints it out. The instructor may. 2. 6. so that the student debugs the program after completing its coding.Practicals Notes: The following instructions about Java practicals should be carried out in the interest of uniformity in their conduct across all the constituent colleges of University of Mumbai. The practical problems must be solved using the best possible methods available on the jdk 1. should be output along with the results.Names of Icecream flavours) extend JInternalFrame and have a method.com website. ________________________________________________________________________ Prop. so that the data structures are not directly accessible from outside of classes. last modification and expiry. 9. editing.2 or 1.1 and 1. Syllabus Page 16 of 29 T. The numeric values output should be preceded by explanatory text. compilation or testing.Practicals. The partly complete program could also contain deliberate errors. All the three classes (ColorPanel: Names of colors inside it. JTextField. which are deprecated by jdk 1. or output it to the screen. 8. 5 Write a program to create a form to enter biodata of student. JTable. Some of the programs could become too long to complete in one lab session. irrespective of whether those methods form a part of the T. 1. The practicals should be performed on the J2SE jdk 1. Exceptions should be generated and exception-handling code should be written wherever necessary. dates of creation. in that case supply a part of the program and ask the student to complete it. which extends JFrame and has three objects of three classes whose name are ColorPanel.Sc. JButton. Use GridBagLayout and GridBagConstraints to lay the components. 2 Define a class that displays information about a file URL like its type. The J2SE jdk 1.2. JScrollPane. encoding. response message and the response code for a Web URL. 3 Build an applet that sends a datagram to a server each time that it is started or stopped. 1. The compilation and execution should be from the bare command prompt available on the Windows 9. Other IDE’s should not be used for program entry. Though there is a substantial correlation between the T.3 platform. Use various components such as JLabel. Comp. 6 (Creating MDI Form in SWING)Design a class. Polymorphism and inheritance should be implemented wherever necessary.Sc.B. Use anonymous inner classes to implement event listeners. (Theory) Advanced Java-I and/or Advanced Java-II syllabus or not. Methods available in jdk 1.B. In each program. which are displayed on the click of the menu bar item. CitiesPanel. 3.3 is downloadable from the java.0. Group I Advanced Java .Y.Sc. 1. The main JFrame has an object of JDesktopPane and this object holds the three panels. The drawing should be cleared when a key is pressed and the line colour should be selectable.1. PRACTICALS 1 Define a class to download a file from the Internet and either copy it as a file on the local machine.Sc. JOptionButton.

which could take on different shapes. validates it as a number and then makes the numeric value available for further processing. 9 Develop a Java bean that is a 2D shape filled with colour. If more number of records are entered it should be appended to the same file. Also notify the Exceptions thrown by the above program and give appropriate messages there. 12 Create an invisible Java bean that multiplies the values of two of its properties and places the product in a third as a read only property. Assume that the text file is already present. Syllabus Page 17 of 29 T. 8 Create an animation with a single line.Y. 11 Create a Java bean that accepts numeric data as text. 10 Create a Java bean that displays multiple lines of text with margins and alignment.Sc. Also provide start and stop buttons to start and stop the animation. Jan 2005 . 15 Write a servlet that reads the name of the servlet class and its initialisation parameters from a server file and then displays these parameters on the screen. This line should produce an effect of a spinning line. ********* ________________________________________________________________________ Prop. In the same example give option for clock-wise or anti-clock-wise spinning. 16 Write a servlet that redirects the user to a different Web page when an out of sequence Web page is requested by him/her Lab Programs Perform at least Six practicals from programs 1-8 and at least Six from practicals from programs 9-16. The colour changes randomly each time the mouse is clicked on the bean. Reference: Java Examples in a Nutshell – David Flannagan. Also create a button called Insert. 14 Write a servlet that accepts single-valued as well as multi-valued parameters like check boxes and multiple selection list boxes from an HTML document and outputs them to the screen. 13 Write a servlet that accepts text and numbers sent from an HTML document and displays them on screen. This button will insert these data from the form in a text file and later on read the same data and print it. Comp.Sc. Demonstrate the animation on the screen. SPD-O’Reilley (2000). which changes its position in a clock-wise direction.B.7 Create a form using JApplet having 2 fields namely Name and Remarks.

tr. 5. Advance Shell programming I 9. Generating crystal reports 6. (WROX) LINUX & SHELL PROGRAMMING: (The Practicals can be performed in LINUX) 1.NET 2003 – Thearon Willis. Procedure for logging in and out. 2. Creating windows form and Creating a class in VB. 2. b) Validation and error trapping c) Validation Techniques. Syllabus Page 18 of 29 T. Jan 2005 . find. awk 11. ActiveX: a) Using ActiveX controls b) The tabbed dialog control c) Browsing the web form. Searching. head. 3. Minimum number of experiments required is TEN from above. sort. Advanced data handling-FlexGrids. d) Recordsets. Some of the experiments listed above may require more than one turn.NET 8. 4. Study of Commands: grep. b) Creating database files for Use by VB c) Using the Data Control.0 by Julia Bradly & Anita Millspaugh (TMH) Beginning VB. b) Adding a Look up table and Navigation. d) Viewing the database file. ex. Visual Basic . ln.B. Editors In Linux: vi. 7. ls.Sc. rm. The teacher should decide and allot the time required for each title listed above 2.NET 9. 3. General Purpose Utilities. Validation. System Administration I: ________________________________________________________________________ Prop. LINUX Installation (Demo Practical) Working in LINUX – Introduction to GUI and Command line interface. cat. 3. Study of filter commands: od. 5.GROUP: II VISUAL BASIC. directory related commands 4. Understanding File System. tail. wc.Sc. cmp. Preventing Errors. 12. Accessing Database files: a) Databases supported by VB 6. sed. file. 8. Selection and SQL: a) Displaying Data in Grids. Comp. LINUX & SHELL Programing Practicals VISUAL BASIC 6. et al. and split. c) Updating a Database File.x 1. Basic LINUX file related commands: touch. e) Reordering a Table Recordset f) Creating a New Dynaset Using SQL. Filtering and sorting data.NET 7. Reference for above practicals: Programming in VB 6. Connecting to a database 10. Creating a Simple Chat Application using WinSock. creation of user account. Study of Commands: more. egrep. Advance Shell programming II 10. g) Tracking database Errors. cp.Y. comm. Implementing simple data binding and Implementing complex data binding 11. Implementing Inheritance and Creating Procedures in VB. uniq. diff. Displaying data from multiple tables NOTE: 1. Navigating the Database: a) Using List Boxes and Combo boxes as Data-Bound Controls. fgrep. 6.

12. UNIX SysstemV. Comp. Syllabus Page 19 of 29 T.B. Using Linux by Bill Ball (Que-PHI) ********* ________________________________________________________________________ Prop. Jan 2005 .Sc.4 Concepts & Applications By Sumitabha Das (TMH) 2. References 1.Sc. System Administration II: Minimum six practicals from above should be completed.Y.

Jan 2005 . 9) Write a program to create a status bar & show the status of Caps lock. pie. 14) Write a program to create a calculator application. 10) Write a program to enter the user name & password on dialog box. & also show the status of current mouse coordinates. 12) Write a program to display the records in access database. Read the recorded message and display it on a message box. ellipse. right double click.Group III Visual C++ . left click. 7) Write a program to create a color menu. 8) Write a program to create a shape toolbar. Comp. When you will select OK button then entered information is display on client area.Y. 5) Write a program to fill the rectangle using different types of brushes. left double click. round rectangle. Note: Perform any 12 practicals from the list.Sc.B. Syllabus Page 20 of 29 T.Sc. 3) Write a program to draw different types of shape (line. Num lock keys. Display the selected shape on the client area. 4) Write a program to fill the random color in rectangle when u will press Ctrl + C keys. 11) Write a program to save the record in the file. polygon) using different styles of pen.Practicals Lab Programs 1) Write a program to print the “Hello World” in client area 2) Write a program to count the number of right click. 13) Write a program to create a paintbrush application. 6) Write a program to display a bitmap on client area. And on selection of color the rectangle should fill with respective color. rectangle. ******* ________________________________________________________________________ Prop. 12) Write a program to create a notepad application.

Each student shall do the project individually.B. as indicated by the Gantt chart during project evaluation. like prototyping. S. presentations and quizzes: Given and arranged by the students on the topics in the syllabus and topics on new.B. ________________________________________________________________________ Prop.Sc.Sc.Sc. System Design. A phase is deemed completed only when its documentation is submitted and approved. Group IV Project: Lab session 1: Choosing a topic for project.Y. Lab Session 2: Demo of a complete project General guidelines for project performance evaluation: The student is required to analyze design. though a project with the same title could be given to more than one student. 2. It is highly recommended that the colleges try and obtain the services for external project guides who have working experience of managing projects. Syllabus Page 21 of 29 T.Y. Investigation system requirements. The phases could be suitably modified if the waterfall paradigm is not used for project development or if the project uses Object Oriented techniques.Sc. The project must be completed latest by 31st January of the academic year. as project development is essentially an evolutionary process. The project must be periodically reviewed by the project guide. The system could be implemented either as a traditional system. The student will produce and maintain a Gantt chart from the given schedule. Seminars. Basic components of project.Group IV: Practicals 1.Y.Sc. Jan 2005 . The design phase must finish in the first term so that coding and unit testing could commence during the Diwali vacation. The date of completion of a phase should be brought forward if the changes made are deemed to be errors and not due to additional knowledge gained from a succeeding phase.B. whenever there are no labsessions related to project. Data and Process Modeling.B. an event driven system. Schedule for the project. Program coding and unit testing.. Time management. They should arranged either in the lab or in a classroom which ever is preferable. The chart shall be placed in the project documentation immediately after the Certificate and separate marks are assigned for completing each phase on time. The actual completion of each phase should also be noted on the chart. who should certify the completion of each phase by affixing his signature on a table maintained for the purpose. The minimal phases for the project are: Project search. finalization and allocation. current developments in the software industry. The guides should oversee the project progress on a weekly or fortnightly basis. The date of the signature assumes importance in view of the marks assigned in evaluation for completing each phase on time. The project guide must ensure that changes are necessary due to the knowledge gained in succeeding phases of the project. System integration. The project guide should control iterations if any non-linear technique for project development. or T. is used. Changes in the submitted documents are possible. Program design. who will generate a schedule for the completion of each of the phases of the project and hand it over to the students under his care before the 15th of July in the third year of the Computer Science course. The signed sheet should appear in the project report after the Gantt cart.Y. Comp. A project guide should be assigned to students. The coding and implementation should be in one of the languages/packages that are defined in the Computer Science syllabus of either F. System implementation and acceptance testing. object-oriented system or as a database system. code and implement an actual system.

• Report layout (reproduced from system documentation). • The names of the student and the project guide. degree in Computer Science of University of Mumbai. • Limitations of the present system. Jan 2005 .Sc. tight English explanation where necessary.Sc. • Context diagram of the proposed system. • List of fields or attributes (for DBMS projects) in each file or table. • Program id. The project report should contain the following program documentation (one copy for each program). Class names to be entered for each file in OO systems. The certificate should minimally contain the following information. and that it forms a part of the requirements for completing the B. • Test results. • Reports List with column headings and summary information for each report.The completed project must be reviewed in the in the month of February (or earlier) by the project guide to ensure that it is correctly working. • Screen layouts for each data entry screen. • Top-level DFD of the proposed system with at least one additional level of expansion. • Date of submission and final review of the project. The system code should be available on a disk for evaluation along with the project report.Sc. queried or reports were produced from them. ________________________________________________________________________ Prop. The project report should contain the following system documentation (one copy for the project). The student is expected to present and demonstrate the project to the University examiner. • System flowchart. • Program listing. • Files or Tables (for DBMS projects) list. • System controls and standards. updated. Comp. Syllabus Page 22 of 29 T. The project guide should affix his signature on the certificate after the final review is conducted. • Space for the signature of the University examiner and date on which the project is evaluated. • The Proposed system – Its advantages and features.Y. • Signature of the project guide and the head of department with date along with the department stamp. Add decision tables. • Test data.B. • Data entry screen (reproduced from system documentation). • Organizational Overview • Description of the present system. • Menu Tree • Program List. • System Coding and variable / file / table naming conventions. • Program function explanation. • The fact that the student has successfully completed the project as per the syllabus. • Program level run chart. • The academic year in which the project is done. • Program level pseudocode or flowchart. The University examiner along with the internal guide shall evaluate the project at the time of University practical examinations. • Structure Chart of the System. written to. decision trees. • Program – File Table that shows the files / tables used by each program and the files are read. The examiner should critically evaluate whether the project has been sufficiently tested by going through the test data and test results. • Report formats for each report.

Jan 2005 . Adherences to project schedule : 25 Marks. Project quality :10 Marks.Sc. Syllabus Page 23 of 29 T. ******* 2. 1. from the 'Adherence to project schedule' head for each schedule milestone that is missed by the student. ________________________________________ Total : 25 Marks (Should be evaluated by the External faculty member) The examiner may deduct 2 marks.Y.B. which shall be divided as under. up to a maximum of 10.50 marks are allotted to the project. & Internal demos and presentation ( Should be evaluated by the internal guide on the basis of the yealy performance of the student) Project documentation : 5 Marks. Project presentation : 5 Marks. The examiner may deduct 2 marks from the 'Project quality' head if the test data and results are not sufficiently exhaustive. ________________________________________________________________________ Prop. Comp. Demonstration of working project : 5 Marks.Sc.

0 Tag Reference. Diagram the Site Planning Site Navigation – Creating Usable Navigation.HTML 4.Y. Formatting Tags.7. Document Structure Tags. the document object model.Y. Table Pointers. forms and form elements. Design for the User. Using Text-Based Navigation. Table Tags. Directory Structure. Testing Your Web Site. Event Handlers. Global Attributes. Sc (Computer Science) Year III SUBJECT: Principles Of Web Design & Web Technologies: Applied Component . Computer Color Basic.9) Unit III HTML . Styling with CSS Graphics and Color – File Format Basics. Hyperlinks. Jan 2005 . Image & Image map. Using Graphics-Based Navigation Creating Page Templates – Understanding Table Basics. Design for the Screen Planning the Site – Create a Site Specification. events and event handling.4. List Tags. Using the <IMG> Element.5) Unit II Web Typography – Type Design Principles.B.Sc. Working with Hexadecimal Colors HTML Frames – Understanding Frames. dynamic html and saving state with cookies ________________________________________________________________________ Prop. Build a Web Site Development Team. Analyze your Audience. Creating a Page Template Unit References Code: PWD (Ch 2. windows and frames. Planning Frame Content Publishing and Maintaining Your Web Site – Publishing Your Web Site. Controlling Typography with Cascading Style Sheet. Choosing a Graphics Tool. Form Tags. COMPUTER SCIENCE APPLIED COMPONENT PRINCIPLES OF WEB DESIGN & WEB TECHNOLOGIES AND .NET TECHNOLOGIES CLASS: B. Frame Tags. Identify the Content Goal. Targeting in Framesets.Sc. Objects) Client-Side Java Script Java script in web browser. Attracting Notice to Your Web Site Unit References Code: PWD (Ch 6.T.8.I Periods per week Lecture 2 (1 Period = 50 minutes) Practical 2 Hours 3 Marks 60 40 Evaluation System Theory Examination Practical per year 3 PAPER-I PRINCIPLES OF WEB DESIGN & WEB TECHNOLOGIES Unit I Web Site Design Principles – Design for the Medium. Refining and Updating Your Content.3. Filenames and URLs. Comp.Sc. Executable Content Tags and Style Sheets Unit References Code: ELJO (Ch 3-9) Unit IV Introduction to Java Script (Functions.B. Syllabus Page 24 of 29 T. Frame Syntax. Design for the Whole Site. Controlling Typography with the <FONT> Element.

Linking. ASP Objects. Wrox Press Ltd. Document Type Definitions. B-ASP: Beginners ASP 3. Scripting Objects (creating an instance of scripting object.0 David Buser et. The FileSystemObject object [drive. Jan 2005 .Sc. Types of XML Markup. Problems with HTML & SGML. Using Style Sheets with XML. 13) Unit VI XML . Comp. (Platinum Edition) (PHI) 2.Y. 11-18) Unit V Active Server Pages .Unit References Code: JSDG (Ch 7.B. 12. 7. 8.Server side Scripting and Client-side scripting. folder and file]) Active Data Object (Connection and Recordeset) Unit References Code: B-ASP (Ch 2. 10. 13) References: 1. ELJO: Using HTML 4.Sc. 8. ________________________________________________________________________ Prop. JSDG: Java Script the definitive guide by David Flanagan 4. al.Introduction to XML. Unit References Code: ELJO (Ch 12. PWD: Principles of Web Design by Joel Sklar 3. Creating XML Documents. Syllabus Page 25 of 29 T. XML & JAVA by Eric Ladd & Jim O’Donnell.

NET Framework: Highlights of the . Using Strong Names. Constants. .NET Building Objects: Understanding Objects. OpenDialog. Managed. 2) Unit II .NET Applications Overview of . Comp.NET & ASP.NET Enterprise Servers. 6) Unit III VB. Creating Complex Application.NET Framework Introduction to . The Common Type System. Building Classes. Lists. Using Shared Properties and Methods. The Framework classes Advanced OO Techniques: Building a Favorites Viewer.NET Framework. Jan 2005 . Managed Heap Organization. Comments and Whitespace.NET (Ch 3-8) Unit IV VB. Understanding OOP and Memory Management Building Class Libraries: Understanding Class Libraries.II Periods per week Lecture 2 (1 Period = 50 minutes) Practical 2 Hours 3 Marks 60 40 Evaluation System Theory Examination Practical per year 3 .NET Framework . CLS. Data Types. Unmanaged and Unsafe. Structures.NET Class Framework Unit References PNF (Ch 1. Context Menus Unit References BVB.NET Introduction: Information and Data.NET: Goals of . Loops Working with Data Structures: Arrays. Registering Assemblies. Overview of . The . ColorDialog.NET Unit I . Reusability. String Handling.VB.B.NET Framework. Variables.NET Framework. FontDialog. Reflection API System Classes: Applications of the System Namespaces – WinCV Tool. The Architecture of . What is an Assembly?.NET: .NET TECHNOLOGIES: Applied Component . Using Multiple Forms Displaying Dialog Boxes: MessageBox. Data Storage. CLR. Sc (Computer Science) Year III SUBJECT: . Select Case. Designing Class Libraries ________________________________________________________________________ Prop. 4.NET Framework Memory Management Under the CLR: Common Runtime System.PAPER-II CLASS: B. Common Type Systems. PrintDialog Creating Menus: Understanding Menu Features. SaveDialog.NET Framework. Inheritance.Y. and Collection Classes Unit References PNF (Ch 3. .NET. Building blocks of . Methods Controlling the flow: Making Decisions. Building a Simple Applications. Enumeration.Sc. Creating Menus. Different types of Assemblies. Finalize Working with Runtime: What is MSIL?. Garbage Collection. Storing Variables. Building Lookup Tables with Hashtable Building Windows Application: Responding to Events. The if Statement. Constructors. Garbage Collection Algorithm. Overview of CLR.Sc.NET Building Block Services. Meta Data. Design goals of the . Collections. The Common Language Specification Common Language Runtime: Design goals of CLR. Meta Data. Syllabus Page 26 of 29 T.

Editing Items. 9) Unit VI ASP. AutoPostBack and Web Control Events. Design Time or Runtime.NET Object Model ADO. Jan 2005 . Data Binding Database Programming: ADO. Accessing Data. The AdRotator Class. Selecting Items.NET 2003 – Thearon Willis. XML Validation. Data Binding with Databases DataList. DataGrid. Comp. The ADO.NET Framework – Kevin Hoffman and Jeff Gabriel (SPD) BVBNET: Beginning VB.NET Classes in Action. The Advertisement File.NET Web Form Fundamentals: A Simple Page Applet. Validations. 17) Main References: PNF: Professional . Inheriting Control Behavior.NET. HTML Control Classes. Comparing the Template Controls.NET Classes. Single-Value Data Binding.NET Applications.NET Unit References CRASPNET (Ch 12. 13. Accessing Disconnected Data. Data Binding with Multiple Templates. Paging and Sorting with DataGrid Using XML: XML’s Hidden Role in .Y. 14. Selecting Multiples Tables Data Binding: Introduction. Updating Data. Code-Behind.Creating Your Own Custom Controls: Windows Forms Controls. (WROX) CRASPNET: The Complete Reference ASP. Defining a Select Command. ASP. Assessing Web Controls Validating and Rich Controls: The Calendar Control. XML Display and Transforms. 6. Improving the Currency Converter. Data Binding Unit References BVBNET (Ch 10-13.NET: Introducing ADO.15. The ADO. XML in ADO. Creating a Connection. Characteristics of ADO. Exposing Properties from User Controls.NET Applications: ASP. The AdRotator. Using a Command with a DataReader. Repeated-Value Data Binding. Web Control Classes. Understanding the ASP. 15.NET. and Repeater: Introducing Templates.Sc. Creating a Form Library Accessing Databases: Data Access Components. The Global asax Application File.NET.Sc.NET – Matthew MacDonald (TMH) ________________________________________________________________________ Prop.B.NET ASP.NET Data Access: SQL Basics. The Page Class Web Control: Stepping Up to Web Controls. Syllabus Page 27 of 29 T. Using Templates with the DataList. Understanding Regular Expressions Unit References CRASPNET (Ch 5. et al.NET Overview of ADO. The XML Classes.16) Unit V ASP.NET and Data Management. 7.

Transforming.Sc. COMPUTER SCIENCE APPLIED COMPONENT PRACTICALS GROUP I (A. Syllabus Page 28 of 29 T. Comp.NET Web Form • Creating the default. DHTML) Basic HTML Tags • To study Document Structure Tags • To study Text formatting Tags • To study Phrase formatting Tags • To study Listing Tags Advanced HTML Tags • Table tags • Merging of tables To Study Form tags and Frames tags Client Side Image Mapping Cascading Style Sheet Using Editor Dreamweaver • Creating College home page XML using CSS • Internal DTD • External DTD Form Validation Using Java Script • Window Object • Location Object • History Object ASP • Registration Form • Creating Friends Details Diary ASP • Server Object (To create a text file at server) • To maintain total number of visit to an application Dynamic HTML ASP.Y. Jan 2005 .T.B. ________________________________________________________________________ Prop.B.Sc.aspx Web Form • Creating the life.C.NET • Using a SqlDataReader • Viewing Data from the Database Reading XML Data • Reading a List from an XML File • Reading. and Displaying XML • Nested Data 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 All practicals from above should be performed.) PRACTICAL LIST (HTML.aspx Web Form Adding Functionality to a Web Application • Creating a Page_Load Event Procedure • Creating a Click Event Procedure Validating User Input • Using the RequiredFieldValidator Controls • Using the ValidationSummary Control • Using the CompareValidator Control • Using the RegularExpressionValidator Control Accessing Data with Microsoft ADO. JavaScript.Sc.NET Creating a Microsoft ASP.Y. ASP.

While teaching (as well as while evaluating the student performance) proper emphasis should be given to each of the two aspects.Y. HTML by Xavier (TMH) 3.C. The project (Web-Site) should be uploaded on local & remote servers & be shown on-line to the examiner for evaluation as far as possible.) WEB PROJECT Important Note: The Web development is as much about creativity as about technology. & Internal demos and presentation ( Should be evaluated by the internal faculty member) Project documentation : 5 Marks.B. Jan 2005 . ________________________________________ Total : 20 Marks ( Should be evaluated by the External faculty member) Case Study: To Conceive. case studies based on good sites should be given as illustrative examples while teaching this subject. Demonstration of working project : 5 Marks. (On-line evaluation is advisable to check the cross platform compatibility and other aspects of the project). ________________________________________________________________________ Prop.GROUP II (A. Sun Microsystems. The content creation is as much important as the technical know-how. Netscape etc. Project quality : 5 Marks. 1. References: 1. The Web Programming Desktop Reference (6 in 1) (Que-PHI) 2. ********** 2. Project presentation : 5 Marks. (Upload this web-site on a server) Prepare a project Report & Discuss the designing and issues related to the development of this web site. Online documentation from Microsoft. 40 marks are allotted to the project. design & Implement a complete and integrated Web-site of one existing or hypothetical organization. All the time. There should be external evaluation (Viva) of this project.Sc. The student is expected to present and demonstrate the web project to the University examiner. Comp. which shall be divided as under.Sc. The teacher should encourage the students to get a live project for this purpose for as many students as possible. Note: 1. Adherences to project schedule : 20 Marks. Syllabus Page 29 of 29 T.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.