|
(2008, 2800 words)
The paper examines spam filtering methods including the method of spam filtering based on the analysis of text information embedded in images, and the method that collects user preference information to formulate the rules in the formal language using Boolean logic simplification. Hypotheses on the concept of spam are critically reviewed; the drawbacks of the methods are identified.
(2006, 4000 words)
The paper examines the role of open source software (OSS) in e-commerce identifying its difference from other software products, reviewing the history of its development, describing OSS market, and discussing OSS use in private and pubic sectors, OSS databases, portals, future prospects, etc.
(2006, 3000 words)
This work produces the requirement specification analysis for a software project meeting the requirements of a customer. The customer is a photographic lab, who offers a range of services to customers. The requirements specification analysis describes a model of the existing system, provides use case model diagram(s) defining collections of use cases and their interactions with external actors together with detailed use case descriptions. An entity class list and a class diagram are also presented, followed by a discussion about the non-functional requirements such as usability, dependability attributes, etc. The second part of the work comprises updated use-case and class diagrams. The class diagrams show entity, control and boundary (i.e. GUI) classes. A relational database schema in 3 rd normal form together with an explicit statement of the assumed functional dependencies, and a complete set of DDL statements (CREATE) and a representative set of DML statements (SELECT, INSERT, UPDATE and DELETE) complete the design of the system.
(2006, 3000 words)
The paper examines the use of animation in feature films describing the software tools of creating visual effects, i.e. Maya 3D, 3D Studio Max, Softimage XSI. The software applications are compared; the contribution to film and game development is discussed.
(2005, 2500 words)
The paper reports on the use of CASE (Computer Aided Software Engineering) tools reviewing the history of their development, their aims, objectives, applications, types, etc. The usefulness of CASE tools is assessed outlining their advantages and disadvantages.
(2006, 1000 words)
The paper reports on a project of developing a piece of reusable software between an engine and a library to support the development of card games, involving the choice of a programming language, rules, operations, etc. Theoretical approaches to feasibility study are reviewed; the plan of building a database of resources for potential card game developers is outlined.
(2005, 5000 words)
The paper examines a novel interaction between web users and computer known as ‘embodied agents’, describing its features and evaluating its advantages and disadvantages. Guidelines on the web design are provided including its auditory and visual content, the accessibility of embedded user interfaces, agent appearance and behaviour, user perception, dialogue features, etc. Evaluation and analysis of the embodied agents’ interaction is conducted using the PEFiC model.
(2006, 3500 words)
The paper describes the tools and techniques used in the engineering of an e-commerce web page design reviewing literature on software and website engineering and discussing the types of tools used in constructing a web page, i.e. HTML, XHTML,ASP, PHP, JSP, etc.
(2006, 4000 words)
The paper examines the creation, development and completion of a DVD collection for a bibliographic and publisher database modelled as an XML DTD. Two software packages are reviewed showing the applications of XML\XSLT in order to assist the users of the programme.
(2005, 3000 words)
The paper examines the history of the SCM development and its implementation in different phases of the software life cycle, focusing on the progress and difficulties faced by SCM developers in the past ten years. The issues of versioning control, change control, third-party tools, etc. are discussed.
(2005, 1200 words)
An overview of the agile and other 'extreme' programming design methodologies which have been adopted in recent years; turning conventional design techniques on their heads
(2006, 1500 words)
To include usability testing into a software design cycle potentially requires huge investments of both time and money by companys for apparently little gain or return on investment. Many companies also fail to see the long-term and generally indirect benefits from such an investment; Increased satisfaction, reduced help-desk call load leading to the need for less staff and thus increased profits. Nielson (1989, 1990, 1993) proposed a way for an effective usability analysis to be conducted for less investment of time and money, with a quicker return on investment. He developed what he later called Discount Usability Methods. Heuristic Analyses are methods designed to test the usability of a software interface at a cost much lower than a full usability analysis, but which still gives reliable, consistent results which when implemented, will improve the usability of the software.
(2004, 2900 words)
Software Engineering is all about producing what the customer wants within time and constraints. In real life software quality is really important. In order to give the program good quality and make it work as perfectly as it can, we use an important factor in Software Engineering called 'testing'. It is very important for a company to produce very good design software. Taking this in mind, usually companies spent at least between 30% and 40% of the total project effort on testing. Testing can cost three to five times as much as all other Software Engineering activities combined. This paper will evaluate the progress of software testing fundamentals and techniques for software test case design, made in recent years. Software testing fundamentals define the overriding objectives for software testing. Test case design focuses on a set of techniques for the creation of test cases that meet overall testing objectives.
Page 2>
|
