Which factors are really important for defining a sofware's architecture?? is there in priority between them?


  • I would say Performance , Maintainability and Scalability are probably the highest. A software needs to perform well, an underperforming software is an annoyance and will drive the customers away. 

    Maintainability is also key for post production - if a software architecture is not done keeping maintainability in mind , bug fixes and enhancements can be a nightmare. 

    Scalability is the next thing in line because most products need to grow and change with time, happens with all of them. 

    These one of the main factors that I would keep in mind while designing and architecting software.

  • The factor would be for both Functional and Non-Functional requirement of Software Application. However the important factor would be for Non-Functional i.e. Performance, Scalability, Maintainability, Security. The reason for addressing all nonfunctional requirements is because those are hidden attributes and not addressing these attributes will create problem at later stage. 

    There are also some other related and important attributes to be considered while deciding a particular architecture style for example approach for Integration with external system, communication protocols, deployment pattern etc.

Comments

Post a Comment

Popular posts from this blog

ContextSwitchDeadlock was detected

Image
I have been writing an application that loads large amounts of data into the a database. The process of loading the data into the database goes through several steps requiring a considerable amount of time to complete. The long processing time is not a matter of concern from the application stand point. However, frequently the application throws a "ContextSwitchDeadlock was detected" message that says the following: Message: The CLR has been unable to transition from COM context 0x20450a0 to COM context 0x20452f0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives ...
Read more

Visual Studio setup and deployment projects

Image
This article describes the basics of Visual Studio setup and deployment projects. Subsequent articles will cover advanced topics, including more on custom actions, .NET installer classes, and how to build an upgrade for the product. Introduction Setup and deployment projects have always been a part of the Visual Studio.NET environment. Setup projects can be used to build various deployment packages, most notably Windows Installer setups packaged as MSI files. I’ll start with a basic setup that installs a C# Windows forms program and adds a shortcut to it. First, select  Setup Project , grouped under  Setup and Deployment  in the  Other Project Types  section. Choosing this will give you an empty project for adding your deployment units. With the project selected in Solution Explorer, the  View->Editor  choice gives you a selection that includes  File System  – this is where you add your files and shortcuts. Application Folder ...
Read more

Using SvcUtil.exe to generate the proxy class and config file

Run svcutil.exe specifying metadata address Open the visual studio command prompt or locate the svcutil.exe from the command prompt c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:C# //use above if you want to generate the proxy in c# c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:VB //Use above if you want to generate the proxy in VB To Get the helpwith svcuitl.exe use the following command c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil The output.config and proxy class will be generated in the "c:\programefiles\microsoft sdks\windows\v6.0A\bin"  
Read more