Software Engineering-II

SUBMITTED TO: MR. RASHID ALI.

Muhammad Ali Zargham1076

Assignment no. 1

Oct. 4, 11

Question No.1: There is a little debate that web-based systems and applications (web apps) are different from many other categories of computer applications. State the salient features/attributes of the web apps to highlight these differences. Answer : Powell summarizes the primary differences when he states the web-based systems involve a mixture between print publishing and software development, between marketing and computing between internal communications and external relations, and between art and technology. The following attributes are encountered in the vast majority of web apps. Network-intensiveness: A web app resides on a network and must serve the needs of a diverse community of clients. A web app may reside on the internet (thereby open worldwide communication). Alternatively an application may be placed on an intranet (implementing communication across an organization) or an Extranet (inter-network communication). Concurrency: A large number of users may access the web app at one time. In many cases, the patterns of usage among end-users will vary greatly. Unpredictable load: The number of users of the web app may vary by order of magnitude from day to day. 100 users may show up on Monday, 10,000 may use the system on Thursday. Immediacy: Web-based applications have immediacy that is not found in any other type of software. That is, the time to market for a complete Web site can be a matter of a few days or weeks.3 Developers must use methods for planning, analysis, design, implementation, and testing that have been adapted to the compressed time schedules required for Web app development. Security: Because Web apps are available via network access, it is difficult, if not impossible, to limit the population of end-users who may access the application. In order to protect sensitive content and provide secure modes of data transmission, strong security measures must be implemented throughout the infrastructure that supports a Web app and within the application itself. Aesthetics: An undeniable part of the appeal of a Web app is its look and feel. When an application has been designed to market or sell products or ideas, aesthetics may have as much to do with success as technical design. Content driven: In many cases, the primary function of a Web app is to use hypermedia to present text, graphics, audio, and video content to the end user. Continuous evolution : Unlike conventional application software that evolves over a series of planned, chronologically spaced releases, Web applications evolve continuously. It is not unusual for some Web apps (specifically, their content) to be updated on an hourly schedule.

Assignment no. 1
Question No.2: Describe the requirement gathering methods for web apps.

Oct. 4, 11

Answer: Requirement gathering activity for web engineering may be abbreviated, the over-all requirement gathering objectives proposed for software engineering remain un-changed. Adapted for Web app, these objectives become. Identify content requirements. Identify functional requirements. Define interaction scenarios for different classes of users. The following requirements gathering steps are conducted to achieve these objectives: Ask stakeholders to define user categories and develop descriptions for each category. Communicate with stakeholders to define basic Web app requirements. Analyze information gathered and use information to follow-up with stake holders. Define use-cases that describe interaction scenarios for each user class.

Question No.3: Briefly explain the different types of analysis for web apps. Answer: Four different types of analysis are conducted during Web app: Content analysis: The full spectrum of content to be provided by the Web app is identified. Content includes text, graphics and images, video and audio data. Data modeling can be used to identify and describe each of the data objects to be used within the Web app. Interaction analysis: Use-cases can be developed to provide detailed descriptions of this interaction. Functional analysis: The usage scenarios (use-cases) created as part of Interaction analysis define the operations that will be applied to Web app Content and imply other processing functions. All operations and functions are described in detail. Configuration analysis: The environment and infrastructure in which the Web app resides are described in detail. The Web app can reside on the Internet, an intranet or an Extranet. In addition, the infrastructure (i.e., the component infrastructure and the degree to which a database will be used to generate content) for the Web app should be identified at this stage.