I am assessing whether a .net intranet application system is of acceptable, reasonable quality. My criteria so far for this is on several fronts: - Architecture (e.g., is the architecture n-tier?) - Is the code easy to maintain? - Has the code been written with reuse in mind, or refactored? - Are there...
Posted to
Free For All
(Forum)
by
dbrook007
on
01-04-2008, 12:00 AM
Filed under: ntier, partial classes, persist changes, Report Viewer, solution project, system analysis", System Design, Technical Specification, UI Architecture, UI Framework, UI Process Components, VB, VB Class, VB Classes, vb.net, Web Forms, .NET, 3tier, 3-Tier Architecture, 3-tier programming, approach, architecture, Asp.Net 2.0 : java script, ASP.NET 2.0 NET SQL Server 2005 database connection error, asp.net tuning, assembly, authentication, Basic Architecture Design, Best Practices, bug, business logic layer, caching, Class Design, concurrentcy, Consistency in UI, css, CustomErrorPage, DAL exceptions, data access layer, data access object relational mapping, Data modeling, datagrid, datalogic layer, dataobjects, design pattern, Events, Generics, Globalization, database object, xml, entity, IIS, application state management, performance, Exception Handling, Exception Handling Application Block, Exception Handling Application Block Tutorial, ASP.NET Architecture, sql server, OOP, "system Design", arcitecture, business model, data serialization, GridView, Patterns & Practices, N-Tier, optimization, Reflection, web service, ADO.NET, Asp.Net 2.0, assemblies, Data Concurrency, database, http, methods, Website Problem